Re: using less in a bash script, screen blanking, alternate screen
On Sunday, September 8, 2013 4:00:02 AM UTC-4, Zenaan Harkness wrote: > OK, I have the following script (reduced, just enough to demonstrate > > the problem): > --- test.sh --- > #!/bin/bash > cmd="apt-cache search debian-installer | sort | egrep --color=always -i > debian-installer" > #tput nrrmc # line 3 I don't see the beginning of the thread at the moment, but the tput command wouldn't affect anything with xterm. The titeInhibit resource sounds like (given Sven's hint) what you are looking for. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/71c0b6d9-2df3-4596-8612-c9dc7602f...@googlegroups.com
Re: terminal emulator compatible with Ecma-48
On Monday, April 29, 2013 5:30:03 PM UTC-4, Chris Davies wrote: > Thomas Dickey wrote: > > > What I recall of the PuTTY FAQ (a specific pointer would help) is that > > > it's roughly comparable to rxvt > > > > http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html that's not what I meant by "specific". You stated that > I'd extend that to suggest that most terminal emulators support the > majority of VT220 sequences, not just the VT100 subset. and > The PuTTY FAQ seems to claim that it's either implemented everything > or else documented what it hasn't implemented. This might be a good > starting point. Noting where PuTTY claims/documents the "everything" would be helpful. As I noted, PuTTY's coverage of the escape sequences makes it roughly comparable to rxvt. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ce1c884f-13ef-46b9-ae99-297adb777...@googlegroups.com
Re: terminal emulator compatible with Ecma-48
On Sunday, April 28, 2013 11:30:01 AM UTC-4, Chris Davies wrote: > berenger.mo...@neutralite.org wrote: > > > I know that most terminal emulators support most VT100 escape > > sequences, which are based on ecma-48 > > > > I'd extend that to suggest that most terminal emulators support the > majority of VT220 sequences, not just the VT100 subset. unlikely - I dealt with that a few years ago: http://invisible-island.net/xterm/xterm.faq.html#compare_versions > > > > but as far as I know, they are > > not able to support the full standard. By example, they only support 7 > > bit sequences, and so CSI is 0x1B5B only, were ecma-48 says it can be > > 0x9B too. > > I don't know about this, although a quick test does appear to suggest > that lxterm does not support \x9b as an alternative to \x1b\5b. hmm - lxterm would be vte, which of course does not support 8-bit controls. > The PuTTY FAQ seems to claim that it's either implemented everything > or else documented what it hasn't implemented. This might be a good > starting point. What I recall of the PuTTY FAQ (a specific pointer would help) is that it's roughly comparable to rxvt - implements about 80% of VT100, but is not a VT100 emulator due to differences in the way it does line-wrapping (apparently because at the outset its developers were attempting to match the SCO console). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/317dbada-3dc8-45bf-86cf-a9665c588...@googlegroups.com
Re: finch key-binding doesnt work
On Friday, October 12, 2012 10:50:01 AM UTC-4, houkensjtu wrote: > I installed finch by apt-get install finch. > > Unfortunately all key-binding doesn't work in Xterm. > > Since xterm is the most frequently used term for me, it's quite annoying. I > found on debian bug report log that also other people got same problem. There is not enough information to guess what problem is being reported. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/0c20a2e8-c897-4e84-9149-5c21537c6...@googlegroups.com
Re: have to switch windows back and forth after firefox, gimp, etc. exit
On Tue, 23 Nov 2010, Thomas Dickey wrote:
On Tue, 23 Nov 2010, jida...@jidanni.org wrote:
Help, whenever I close firefox, gimp, etc. (emacs is OK though.) I have
to switch windows back and forth before I can continue typing into the
window I am left starting at. Else my keystrokes are ignored. I use
Debian sid/experimental. pstree says:
|-nodm---xinit-+-Xorg
|
`-nodm---ck-launch-sessi-+-sh---icewm-session-+-icewm---xterm---bash-+-emacs---aspell
| ||
| |-firefox-bin---17*[{firefox-bin}]
and I use http://jidanni.org/comp/configuration/.Xresources
yes... (I noticed this a while back, and it's on my to-do list - appears
to be due to an xorg change, since it doesn't happen on my older systems).
...or application change - for example
http://www.archivum.info/opera.linux/2008-10/00096/Opera-stealing-focus-(attn-Eirik-Byrkjeflot-Anonsen).html
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101125081421.t16...@mail101.his.com
Re: have to switch windows back and forth after firefox, gimp, etc. exit
On Tue, 23 Nov 2010, jida...@jidanni.org wrote:
Help, whenever I close firefox, gimp, etc. (emacs is OK though.) I have
to switch windows back and forth before I can continue typing into the
window I am left starting at. Else my keystrokes are ignored. I use
Debian sid/experimental. pstree says:
|-nodm---xinit-+-Xorg
|
`-nodm---ck-launch-sessi-+-sh---icewm-session-+-icewm---xterm---bash-+-emacs---aspell
| ||
| |-firefox-bin---17*[{firefox-bin}]
and I use http://jidanni.org/comp/configuration/.Xresources
yes... (I noticed this a while back, and it's on my to-do list - appears
to be due to an xorg change, since it doesn't happen on my older systems).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101123103522.u4...@mail101.his.com
Re: keeping the two latest files on a folder
On Thu, 15 Oct 2009, Matthew Smith wrote: Quoth Boyd Stephen Smith Jr. at 14/10/09 23:12... Your font has betrayed you. The single-column-mode option is "-1" (dash-one), your messages says you tried the option "-l" (dash-ell) which requested a detailed (long) listing. Aha! Sure looked like a lower-case L. Think I need to bump up the font size for this little screen! Thank you for pointing that out. Unfortunately, I still can't get the desired effect. The ls -1 (#1) gives me my single-column list but piping it to sed '1,2d' still gives me the entire directory listing, each item separated by a single space. Can't see any reason from the sed manpage why this should be and can't locate my awk & sed book (may have left it at last job.) ls -1 |sed '1,2d' gives me a single column. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: recent xterm/terminal(?) change (control-C) shows ^C?
On Thu, 17 Sep 2009, Justin Piszcz wrote: Hello, Distribution: Debian Testing Recently, after an apt-get dist-upgrade, when I hit control-c, I get the following in an xterm: $ ^C It occurs with aterm/xterm, bash and csh. It's not related to versions of xterm (noting "aterm" above, and checking older versions of xterm). Before, when I hit control-c, it would not show ^C on the console (makes it easier when copying/pasting items from the command line) I never recall this occurring before-- does anyone which character mappings are responsible for this? I don't see it with tcsh, but do see it with bash. (my "csh" is tcsh, according to the /etc/alternatives link). My stty settings in tcsh and bash are identical, e.g.: speed 38400 baud; rows 42; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke However, since I see a difference between bash and tcsh, the issue may not in some other place (don't known...) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: looking for packages versions of running daemons
On Fri, 11 Sep 2009, Thomas Dickey wrote: On Fri, 11 Sep 2009, Thomas Dickey wrote: however, Debian's packagage maintainer for mawk has not responded to any of package... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: looking for packages versions of running daemons
On Fri, 11 Sep 2009, Thomas Dickey wrote:
On Fri, 11 Sep 2009, Javier Barroso wrote:
On Thu, Sep 10, 2009 at 11:33 PM, Cameron Hutchison wrote:
/proc/pid/cmdline usually has ASCII NUL separated fields, which awk does
not split, so usually you have to use xargs -0. I noticed some cases
where the args were space separated (perl script), so I needed awk for
that case. I'll look more into awk and see if it can handle NULs in
some way. It doesn't by default.
Ok, I didn't know that. Thank you for the explication
awk -F '\000' '{print $1;exit}' /proc/$pid/cmdline
That depends on whether you're using gawk (which provides a non-POSIX
extension for nulls), or mawk.
fwiw, this example works with current mawk - here:
http://invisible-island.net/mawk/
however, Debian's packagage maintainer for mawk has not responded to any
of the fixes which I've made over the past year.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: looking for packages versions of running daemons
On Fri, 11 Sep 2009, Javier Barroso wrote:
On Thu, Sep 10, 2009 at 11:33 PM, Cameron Hutchison wrote:
/proc/pid/cmdline usually has ASCII NUL separated fields, which awk does
not split, so usually you have to use xargs -0. I noticed some cases
where the args were space separated (perl script), so I needed awk for
that case. I'll look more into awk and see if it can handle NULs in
some way. It doesn't by default.
Ok, I didn't know that. Thank you for the explication
awk -F '\000' '{print $1;exit}' /proc/$pid/cmdline
That depends on whether you're using gawk (which provides a non-POSIX
extension for nulls), or mawk.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: How to install updated terminfo entry in home directory?
On Mon, Sep 07, 2009 at 07:00:08PM +0200, Otto Maddox wrote: > I have been having DEL/delete/backspace problems, the cause of which I > have traced to the following bug report: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319554 > > In summary, version 5.5-5 of libncurses5 (and libncurses5-dev) is > installed on this system, it has an incorrect terminfo entry for > xterm-color, and I have no superuser privileges to upgrade it. > > Can somebody please tell me how I can get the latest Debian-compatible > terminfo entry for xterm-color and install it in my home directory? ncurses manpage describes TERMINFO and TERMINFO_DIRS environment variables which override ncurses' search for terminal descriptions. Setting TERMINFO, you can override tic's target for installing updated terminal descriptions. infocmp provides a copy of a terminal description which can be edited. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: xterm font sizes choices?
On Wed, Apr 08, 2009 at 09:10:21AM +0200, Cameron Hutchison wrote: > zhang zhengquan writes: > > >Thanks, then maybe 10x20 is just small for me... > > To verify that the correct resources are being used, run > "xterm -fn 10x20". This will start an xterm with that font, > or display an error that it cannot find the font. > > If this gives you a different font to what you normally get > then you will need to see what is wrong with your loading of > resources. One thing that comes to mind is that you may be > using uxterm, with a resource class of UXTerm. That's likely - OP is using a wildcard in the font resource: XTerm*font: 10x20 This would work: XTerm*vt100.font: 10x20 -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpheNKS2FJY5.pgp Description: PGP signature
Re: mouse and gpm
On Fri, Mar 27, 2009 at 08:20:12AM +0100, Daniel Dalton wrote: > On Tue, Mar 24, 2009 at 04:57:15PM -0400, Thomas Dickey wrote: > > I hadn't really thought about gpm in particular, but wheel mice are > > doable with the extension I added a few years ago, and have tested in > > xterm (which is a binary change). > > > > That part is something that Daniel Baumann is steering toward > > in ncurses updates. > > So what do I need exactly? Can I keep using GPM? And if necessary I can > apply patches and build from source... a) you can continue using gpm. b) ncurses updates will sooner or later support wheel mice c) whether gpm supports wheel mice is not entirely clear -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpbYbxIr2NS1.pgp Description: PGP signature
Re: mouse and gpm
On Tue, Mar 24, 2009 at 12:50:17PM +0100, Chris Bannister wrote: > On Sun, Mar 22, 2009 at 07:42:44PM +1100, Daniel Dalton wrote: > > Hi, > > > > I'm using a mouse with gpm and brltty, and it is working well... Is it > > possible to get the scroll wheel on my mouse to scroll the terminal in > > text mode? eg. work like the page up and page down keys, maybe not as > > bigger chunks though... Thought it could be cool to scroll emacs buffers > > and the like with a mouse under text mode? > > > > Is this possible with gpm? > > I think the next/new ncurses will allow this sort of thing. Maybe Thomas > Dickey has more info. He seems to magically pop in if xterm or lynx is > mentioned in a post. :) google (though as time passes, it's more and more spotty in its coverage) I hadn't really thought about gpm in particular, but wheel mice are doable with the extension I added a few years ago, and have tested in xterm (which is a binary change). That part is something that Daniel Baumann is steering toward in ncurses updates. For gpm specifically - that would still require some change (but doesn't require a whole new version of ncurses). Someone a few months ago stated that there's some patch (or configuration) where gpm would deliver button 4/5 events sort of like xterm, but looking at the gpm.h header, the only comments regarding wheel mice say it's not clear: /*... Cfg buttons */ /* Each button has one bit in the 16 bit buttons field. * Mouse movement and wheel movement are not associated with a button * i.e. buttons=GPM_B_NONE in these cases * (except for ms3 mouse, for reasons unknown?) * The middle button if pressed down (or clicked) is independent of * the wheel "device" which it happens to be associated with * The use of GPM_B_UP/DOWN with ms3 is unclear. Maybe the wheel * could be rolled forward then backward * and this would generate a 'click' event on 'button 5' GPM_B_UP, * but really the expected behaviour of wheel is movement, typically * used for jump scrolling or for jumping between fields on a form. */ #define GPM_B_DOWN 32 #define GPM_B_UP16 #define GPM_B_FOURTH8 #define GPM_B_LEFT 4 #define GPM_B_MIDDLE2 #define GPM_B_RIGHT 1 #define GPM_B_NONE 0 (since gpm's documentation is its source code...) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpvfdZ4qCd7U.pgp Description: PGP signature
Re: help with mlterm
On Mon, Jan 26, 2009 at 01:30:07AM +0100, David Purton wrote: > Becuase complex charaters become hard to read, especially at small point > sizes. Bold is set to be a different colour, I don't need a different > typeface as well. Many terminals have the option to disable bold fonts - > it's just a preference thing. It's esp odd since I can specify a > completely different type face for bold fonts in mlterm using aafont, > but it still chooses the bold variant of that family no matter what! You might be able to make it use a terminal description that pretends to not support bold font (though there are always things like "ls" which ignore termcap/terminfo). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpUoN3wM69y9.pgp Description: PGP signature
Re: lynx and readme.gz
On Mon, Dec 01, 2008 at 08:20:07AM +0100, lee wrote:
> On Sun, Nov 30, 2008 at 05:46:26PM -0500, Thomas Dickey wrote:
> > On Fri, Nov 28, 2008 at 03:30:09AM +0100, lee wrote:
> > > The web page looks good --- but it seems to tell me that it isn't
> > > possible to have a setting to reject all cookies in the
> > > ~/.lynxrc. Lynx itself won't save that setting, either, and I'm tired
> > > of changing the setting every time myself.
> >
> > Which setting is that? (If it's in the "options" menu, that can be changed
> > using the ENABLE_LYNXRC feature).
>
> The one I change? That's in the options menu. There's a footnote or so
> in the options menu saying that some of the settings will not be
> saved, and the cookie setting is one of them.
The ENABLE_LYNXRC settings in lynx.cfg override those. Sounds like you're
talking about this section:
Security and Privacy
Cookies : [ask user__]
Invalid-Cookie Prompting (!) : [prompt normally___]
SSL Prompting: [prompt normally___]
If you have this in lynx.cfg
ENABLE_LYNXRC:force_cookie_prompt:ON
then the screen changes to this:
Security and Privacy
Cookies : [ask user__]
Invalid-Cookie Prompting : [prompt normally___]
SSL Prompting: [prompt normally___]
By the way, lynx will read whatever config-file you have in the $LYNX_CFG
environment variable. My $LYNX_CFG points to a file that begins
include:lynx.cfg
so I don't have to edit the system's copy...
> > > So how do you make lynx display gziped files?
> >
> > Actually you tell lynx to tell the server that it can display gzip'd files.
> > Then (if the server cooperates), it'll deliver gzip'd files, and lynx
> > will display them.
> >
> > .h2 PREFERRED_ENCODING
> > # When doing a GET, lynx tells what types of compressed data it can
> > decompress
> > # (the "Accept-Encoding:" string). This is determined by compiled-in
> > support
> > # for decompression or external decompression programs.
> > #
> > # Values for this option are keywords:
> > # NONEDo not request compressed data
> > # GZIPFor gzip
> > # COMPRESSFor compress
> > # BZIP2 For bzip2
> > # ALL All of the above.
> > #PREFERRED_ENCODING:all
> >
> > (not all servers cooperate - and of course lynx _could_ be built without
> > gzip support - but this is where it's configured at runtime in lynx).
>
> Hm, I put that into ~/.lyncrc, with PREFERRED_ENCODING:all enabled
> ("#" removed). Starting lynx in an xterm and following a link to a
> gziped file brings up and archive manager. Doing the same on a console
> makes lynx offer me to either download the file or to cancel.
You can see (at least) part of the problem using lynx's -trace option
(or toggling to trace with ^T). Lynx should be sending a header saying
what it's accepting, and the server will tell what it's sending.
Beyond that, it's up to the server to recognize the content type,
and for lynx to recognize what type of presentation to use.
> That is using apache2, running on the same host. I didn't change the
> apache configuration in regard to this.
>
> Why does the server need to cooperate? It can send the file in any
> case, and lynx could just offer to download or to display it, or to
> cancel.
lynx could - but it's based on the mime type that the server tells lynx.
For example...
I looked around, found some gzip'ed files on my homepage - which the
server only says application/x-gzip - for instance. That's the
content-type which shows up in the "Lynx.trace" file if you use the
"-trace" option, or toggle trace on with ^T (control/T).
The server says
HTMIME: Date: Tue, 02 Dec 2008 00:55:31 GMT
Server: Apache/2.0.52 (CentOS)
Last-Modified: Mon, 01 Dec 2008 00:43:57 GMT
ETag: "17fc2b2-189cf-8189ad40"
Accept-Ranges: bytes
Content-Length: 100815
Connection: close
Content-Type: application/x-gzip
The "Content-Type" is useful -
But lynx is (following the rules outlined in the various RFCs)
looking for a line giving the "Content-Encoding", e.g.,
Content-Encoding: gzip
That doesn't appear, so lynx offers to download it. For local and ftp
files, lynx doesn't have that to look
Re: lynx and readme.gz
On Fri, Nov 28, 2008 at 03:30:09AM +0100, lee wrote: > On Thu, Nov 27, 2008 at 04:07:50PM -0500, Thomas Dickey wrote: > > On Tue, Nov 25, 2008 at 04:40:07AM +0100, lee wrote: > > > Hm, there seem to be lots of options in lynx.cfg, but almost > > > everything is disabled. The file has 3569 lines, but only 34 lines are > > > not empty and don't start with a "." or a "#". And there is no manpage > > > about lynx.cfg. > > > > Most of those "3569 lines" are comments which document lynx.cfg > > They can be formatted into a hypertext document > > (which doesn't appear to be part of the Debian package). > > There's an example here: > > > > http://lynx.isc.org/release/lynx2-8-6/lynx_help/cattoc.html > > Ok, 628 lines don't seem to be comments but options, of which 34 are > explicitly set. That still doesn't tell me how to enable lynx to > display the files I would like to read. > > The web page looks good --- but it seems to tell me that it isn't > possible to have a setting to reject all cookies in the > ~/.lynxrc. Lynx itself won't save that setting, either, and I'm tired > of changing the setting every time myself. Which setting is that? (If it's in the "options" menu, that can be changed using the ENABLE_LYNXRC feature). > So how do you make lynx display gziped files? Actually you tell lynx to tell the server that it can display gzip'd files. Then (if the server cooperates), it'll deliver gzip'd files, and lynx will display them. .h2 PREFERRED_ENCODING # When doing a GET, lynx tells what types of compressed data it can decompress # (the "Accept-Encoding:" string). This is determined by compiled-in support # for decompression or external decompression programs. # # Values for this option are keywords: # NONEDo not request compressed data # GZIPFor gzip # COMPRESSFor compress # BZIP2 For bzip2 # ALL All of the above. #PREFERRED_ENCODING:all (not all servers cooperate - and of course lynx _could_ be built without gzip support - but this is where it's configured at runtime in lynx). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpjLuTrcoSkx.pgp Description: PGP signature
Re: lynx and readme.gz
On Tue, Nov 25, 2008 at 04:40:07AM +0100, lee wrote: > Hm, there seem to be lots of options in lynx.cfg, but almost > everything is disabled. The file has 3569 lines, but only 34 lines are > not empty and don't start with a "." or a "#". And there is no manpage > about lynx.cfg. Most of those "3569 lines" are comments which document lynx.cfg They can be formatted into a hypertext document (which doesn't appear to be part of the Debian package). There's an example here: http://lynx.isc.org/release/lynx2-8-6/lynx_help/cattoc.html -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpT3NQB63slu.pgp Description: PGP signature
Re: lynx and readme.gz
On Mon, Nov 24, 2008 at 06:40:04AM +0100, lee wrote: > On Sun, Nov 23, 2008 at 10:47:23PM -0500, Douglas A. Tutty wrote: > > On Sun, Nov 23, 2008 at 08:04:22PM -0600, lee wrote: > > > how do I configure lynx to display or to have an option to display > > > gziped files (like README.Debian.gz) instead of only offering to > > > download them? > > > > I'm not sure how you set it _not_ to. I just right-arrow over the link > > and read them. > > > > Sorry for the "works for me" post. However, at least you know that it > > should work. > > Well, I didn't set it ... It can depend on the web server[1] --- but > can lynx do it? > > > [1]: http://httpd.apache.org/docs/2.0/mod/mod_deflate.html gzip and deflate are different flavors (lynx can do it - provided that the server labels them correctly - some servers don't). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpiwGaaQK8sB.pgp Description: PGP signature
Re: lynx upgrade issue?
On Fri, Aug 22, 2008 at 02:20:09AM +0200, i'll teach you to turn away. wrote: ... > ...where'd i go wrong? I don't _see_ the problem. But when I'm puzzled by a configuration problem with lynx, I use the trace options to see what it is actually loading. You should be able to do oldlynx -trace -trace-mask=8 . and (quitting lynx), see in your home directory Lynx.trace, containing info such as this: LYReadCFG COLOR:6:brightcyan:black lynx_chg_color(color=6, fg=14, bg=0) lynx_map_color(6) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgp1i75oJ2VAL.pgp Description: PGP signature
Re: lynx upgrade issue?
On Mon, Aug 18, 2008 at 01:50:19PM +0200, i'll teach you to turn away. wrote: > Thomas Dickey <[EMAIL PROTECTED]> wrote: > TD> On Thu, Aug 14, 2008 at 07:30:17AM +0200, i'll teach you to turn away. > wrote: > >> Configuration file "3D3D/tmp/lynxcfg22579" is not available. > TD> That's mime-encoding (a nuisance to get rid of unless your newsreader > TD> understands the attachments). Here's another try (omitting the signature > TD> which triggered the wrapping): > > gotcha. ok, so it loads lynx now without incident, but it's still > using default oldlynx colors, which is at least a step better than default > NEWlynx colors. i have my colors in ~/.lynx/colors as someone else had > mentioned in this thread, but no matter where in /etc/lynx* i copy my > COLOR:0et.al stuff, it doesn't seem to affect what colors it actually > uses. so what's next? please & thanks. :) Some people would modify the file under /etc - but that's not necessary. I set $LYNX_CFG to point to my own file, and put at the top include:lynx.cfg and then in that file, modify the color settings. For example: COLOR:6:brightblue:green The advantage to doing it that way, is less tinkering with installed files. To see what lynx.cfg file is installed, I'd look at dpkg output (-l to find the package name, -L to look at the list of files). As someone notes, lynx-cur installs /etc/lynx-cur/lynx.cfg -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lynx upgrade issue?
On Thu, Aug 14, 2008 at 07:30:17AM +0200, i'll teach you to turn away. wrote:
> Thomas Dickey <[EMAIL PROTECTED]> wrote:
> TD> You don't have to run it with root: "oldlynx" is a script that calls lynx.
> TD> So you could put "oldlynx" in your path and just run it...
>
> $ oldlynx
> ./oldlynx: line 9: 3D/tmp/lynxcfg22579: No such file or directory
> ./oldlynx: line 13: 3D/tmp/lynxcfg22579: No such file or directory
> ./oldlynx: line 14: 3D/tmp/lynxcfg22579: No such file or directory
>
> Configuration file "3D3D/tmp/lynxcfg22579" is not available.
That's mime-encoding (a nuisance to get rid of unless your newsreader
understands the attachments). Here's another try (omitting the signature
which triggered the wrapping):
#!/bin/sh
# invoke lynx built with color-style, overriding the color options to use the
# non-color-style scheme -TD
my_cfg=${TMPDIR:-/tmp}/lynxcfg$$
trap "rm -f $my_cfg" 0 1 2 5 15
rm -f "$my_cfg"
echo "DEFAULT_COLORS:off" >>$my_cfg
if test -n "$LYNX_CFG" ; then
echo "include:$LYNX_CFG" >>$my_cfg
fi
echo "COLOR_STYLE:" >>$my_cfg
echo "NESTED_TABLES:off" >>$my_cfg
LYNX_CFG=$my_cfg
export LYNX_CFG
unset LYNX_LSS
${LYNX_PROG-lynx} "$@"
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lynx upgrade issue?
On Sat, Aug 09, 2008 at 02:10:07AM +0200, i'll teach you to turn away. wrote: > Thomas Dickey <[EMAIL PROTECTED]> wrote: > TD> On Tue, Aug 05, 2008 at 11:10:17PM +0200, i'll teach you to turn away. > wrote: > TD> If lynx thinks there's no color-style file, it'll construct a style from > TD> the "COLOR" settings that mimics the non-color-style. (It's done that > TD> way intentionally, to let most of the people who want the old style to > TD> use it). ... > thomas, i know you're awesome. & i know you're trying really hard > to help me. for some reason, my brain is broken on this. i do not > understand how you want me to apply the oldlynx script into the current > config, or where to point to it, or... anything really. am i just supposed > to run the oldlynx script with root & let it ...do what it's going to do? You don't have to run it with root: "oldlynx" is a script that calls lynx. So you could put "oldlynx" in your path and just run it... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpNlIh2snDjo.pgp Description: PGP signature
Re: lynx upgrade issue?
On Tue, Aug 05, 2008 at 11:10:17PM +0200, i'll teach you to turn away. wrote: > Thomas Dickey <[EMAIL PROTECTED]> wrote: > TD> On Thu, Jul 31, 2008 at 08:00:21PM +0200, i'll teach you to turn away. > wrote: > >> there's nothing in there about color_style. in fact, the only > >> thing in the entire directory about color_style is in > >> /etc/lynx-cur/lynx.cfg.dpkg-dist, whatever that is. & it's already > >> commented out: > >> #COLOR_STYLE: lynx.lss > TD> The commented-out values correspond (or should...) to the default values > TD> compiled into lynx. > > ...but i don't want the default values. isn't that the point? yes (that's what the replies to your posting are addressing). The commented-out values are part of the documentation, to show what the default values are as well as to illustrate the syntax. > >> COLOR_STYLE: ~/.lynx/colors > TD> The data in the COLOR_STYLE file is organized differently from lynx.cfg > > yes, i agree... so how do i get them to relate? If lynx thinks there's no color-style file, it'll construct a style from the "COLOR" settings that mimics the non-color-style. (It's done that way intentionally, to let most of the people who want the old style to use it). > TD> The "oldlynx" script (which may be part of the package) suppresses the > TD> color-style file, which makes it look very close to the old version. > > ok, but how do i make it recognize this, or...? my apologies, i'm > a bit lost on what to do next. The original text (removing the "> TD> " for instance) is a shell script named "oldlynx" in the samples directory of lynx, e.g., http://lynx.isc.org/lynx2.8.6/lynx2-8-6/samples/oldlynx The script constructs a temporary copy of lynx.cfg, overrides a few settings to produce a screen that looks much like the non-color-style lynx. > TD> For reference (the script): ... I named it "oldlynx" to make it very simple; with some minor tinkering it could be named "lynx" and told to run "lynx.cur", for example. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpqsTcFwNBid.pgp Description: PGP signature
Re: lynx upgrade issue?
On Thu, Jul 31, 2008 at 08:00:21PM +0200, i'll teach you to turn away. wrote:
> # local overides for lynx-cur configuration
> STARTFILE:http://www.debian.org/
> NNTPSERVER:cis.dfn
>
> there's nothing in there about color_style. in fact, the only
> thing in the entire directory about color_style is in
> /etc/lynx-cur/lynx.cfg.dpkg-dist, whatever that is. & it's already
> commented out:
>
> #COLOR_STYLE: lynx.lss
The commented-out values correspond (or should...) to the default values
compiled into lynx.
> so anyway, taking the Logical Next Step, i added this to
> /etc/lynx-cur/local.cfg:
>
> COLOR_STYLE: ~/.lynx/colors
The data in the COLOR_STYLE file is organized differently from lynx.cfg
>
> ...& lynx still totally ignores it. :( i hate the new colors, i
> can't get them to do exactly what old lynx did, & it's making me crazy.
> any other suggestions?
The "oldlynx" script (which may be part of the package) suppresses the
color-style file, which makes it look very close to the old version.
For reference (the script):
#!/bin/sh
# invoke lynx built with color-style, overriding the color options to use the
# non-color-style scheme -TD
my_cfg=${TMPDIR:-/tmp}/lynxcfg$$
trap "rm -f $my_cfg" 0 1 2 5 15
rm -f "$my_cfg"
echo "DEFAULT_COLORS:off" >>$my_cfg
if test -n "$LYNX_CFG" ; then
echo "include:$LYNX_CFG" >>$my_cfg
fi
echo "COLOR_STYLE:" >>$my_cfg
echo "NESTED_TABLES:off" >>$my_cfg
LYNX_CFG=$my_cfg
export LYNX_CFG
unset LYNX_LSS
${LYNX_PROG-lynx} "$@"
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
pgpxAc2BnACfp.pgp
Description: PGP signature
Re: terminal resize doesn't propagate to an application
On Tue, Jul 01, 2008 at 09:29:36PM -0300, Henrique de Moraes Holschuh wrote: > On Tue, 01 Jul 2008, Thomas Dickey wrote: > > On Tue, Jul 01, 2008 at 09:20:14PM +0200, Henrique de Moraes Holschuh wrote: > > > On Tue, 01 Jul 2008, Ron Johnson wrote: > > > > IIRC, there's a (Debian-specific?) bug in ncurses regarding WINCH. > > > > > > Is it reported? That's an extremely annoying bug that is asking to be > > > stomped with extreme prejudice... > > > > > > If you're running under su, it hits really really often. > > > > If you're su'd, signals generally are blocked. > > Even WINCH? That's surprising (to me, anyway). I just tried it and it apparently not WINCH (am at home to check). Other signals are though. I suppose it's in a manpage somewhere. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpDO2ECxEKq2.pgp Description: PGP signature
Re: terminal resize doesn't propagate to an application
On Tue, Jul 01, 2008 at 09:20:14PM +0200, Henrique de Moraes Holschuh wrote: > On Tue, 01 Jul 2008, Ron Johnson wrote: > > IIRC, there's a (Debian-specific?) bug in ncurses regarding WINCH. > > Is it reported? That's an extremely annoying bug that is asking to be > stomped with extreme prejudice... > > If you're running under su, it hits really really often. If you're su'd, signals generally are blocked. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpKcP5jgXaiR.pgp Description: PGP signature
Re: terminal resize doesn't propagate to an application
On Tue, Jul 01, 2008 at 08:00:32AM +0200, Ron Johnson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/30/08 15:47, Martin Kraus wrote: > > hello, > > I've got a problem with resizing terminal windows. The information about > > terminal resizing doesn't always reach the application running inside the > > terminal. I thought it's the problem with blocked WINCH signal, but now I've > > found out that it works in about 80% of the cases. If it doesn't work > > additional resizes of the term window usualy propagate to the application. > > > > Is there any way to trace signals that get sent between terminal > > application > > and process running inside the terminal? I thought using strace on the > > terminal to see if it sends WINCH signals but I can't seem to find it in the > > output. However I don't know what exactly to look for. > > IIRC, there's a (Debian-specific?) bug in ncurses regarding WINCH. I took a look, but didn't see one... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What am I missing without mutt?
s. keeling <[EMAIL PROTECTED]> wrote: > Michelle Konzack <[EMAIL PROTECTED]>: >> Am 2008-02-10 19:26:30, schrieb Tzafrir Cohen: >> > On Sun, Feb 10, 2008 at 09:09:55PM +0200, Dotan Cohen wrote: >> > >> > > No. I have no need for Arabic, really, I was just checking how Arabic >> > > is displayed on the console for Ron Johnson. I do have need for >> > > Hebrew, however, and typing it on the console comes out LTR. I would >> > > like to get libfribidi working. >> > >> > Try mlterm . >> > >> > (The verb "try" is appropriate here, as mlterm is a bit buggy). >> >> Hmmm, I do not remember since when, but maybe since Potato? >> >> It seems, "mlterm" will be never run stable. before this >> happen Thomas Dickey has added bidi support to XTerm... :-) I revisit it periodically. There was a patch (I do have a copy), but not useful due to licensing - it relied on GPL libraries. Supposedly the library license was changed to LGPL, but read that it wasn't done with the agreement of all contributors. (I'll pick through the thread for more details ;-) >> (Maybe he read this stuff) > I believe he Kibos "xterm", as I often see him pop up wherever it's > mentioned. Hi Thomas. :-) You're one exceptionally dilligent > maintainer. Much appreciated. > He should be here any second now to sort htis out. google helps (not as much as it used to - looks like the google-bias is filtering out almost all of the ongoing usenet comments). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: discovering debian ...
oxy <[EMAIL PROTECTED]> wrote:
> Hi, i just installed debian/gnome and am discovering it.
> At first, few things sound strange:
> where is man here? There is only a strange xman :-[
> The /usr/share/man is actually there ...
> an apropos? whatis?
> `xtem --help` says that `xterm -fs 14` should work, but the font size
> does not change!
Actually it doesn't say _that_ ("xterm -help" lists the available options).
man xterm gives more words:
-fa pattern
This option sets the pattern for fonts selected from
the FreeType library if support for that library was
compiled into xterm. This corresponds to the
faceName resource. When a CJK double-width font is
specified, you also need to turn on the cjkWidth
resource.
-fs size
This option sets the pointsize for fonts selected
from the FreeType library if support for that
library was compiled into xterm. This corresponds
to the faceSize resource.
The "-fs" option does nothing if the "-fa" option (or "faceName" resource)
is not given. The default uses the bitmap fonts.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lynx configuration
hce <[EMAIL PROTECTED]> wrote: > I've just installed lynx. I am a vim user and I like to use vim key > map on lynx and use the same terminal background color (black) in lynx > (lynx uses gray background by default) when I start the lynx. It's set in the lynx.lss file (see the comment at the top of that file). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Terminal issues in fresh install
David <[EMAIL PROTECTED]> wrote: > Thomas Dickey wrote: >> Daniel Burrows <[EMAIL PROTECTED]> wrote: >> >>> IIRC there was a situation a few years ago where you had to install a >>> Unicode-enabled xterm, pass "-u", or both. Sarge dates to 2005; I'm sure >>> that there were X terminals in 2005 that could handle UTF-8, but I don't >>> know if the default xterm did. >> >> xterm's supported UTF-8 since 1999: >> >> http://invisible-island.net/xterm/xterm.log.html >> >> (likewise, it's been possible to change the encoding) >> > Default xterm doesn't but if you want xterm with utf-8, that's another > xterm install option. hmm - the context is Debian (not the configure-script defaults). iirc, Debian's packaged xterm using the wide-character support since 2002 or so. (Unsure what else you could mean by "another xterm install option"). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Terminal issues in fresh install
Sven Joachim <[EMAIL PROTECTED]> wrote: > On 2008-01-01 20:57 +0100, Daniel Burrows wrote: >> Note that just changing the environment variable inside the terminal >> won't help -- it's the terminal that needs to interpret those sequences, >> so you have to run *the terminal itself* in the new locale. > Some terminals also allow to change the encoding at runtime, e.g. KDE > konsole or putty. xterm does that as well (control sequences, or menu entry) It doesn't adjust the fonts though, so it's possible to start it with an ISO-8859-1 font and switch to UTF-8, making it recognize but not display various characters. That's the point of the uxterm script - to make it simple. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Terminal issues in fresh install
Daniel Burrows <[EMAIL PROTECTED]> wrote: > IIRC there was a situation a few years ago where you had to install a > Unicode-enabled xterm, pass "-u", or both. Sarge dates to 2005; I'm sure > that there were X terminals in 2005 that could handle UTF-8, but I don't > know if the default xterm did. xterm's supported UTF-8 since 1999: http://invisible-island.net/xterm/xterm.log.html (likewise, it's been possible to change the encoding) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: vi issue in etch
Joseph L. Casale <[EMAIL PROTECTED]> wrote: > While you are at it, consider using vim instead of vi unless you have a good > reason not to do so. this statement leads naturally into the next: > Well, therein lies my lack of experience! I didn't even know there was a > difference, vim is what I "meant" to use but didn't know I wasn't, hence the > apt-get install vim made it all good! :) (people lacking experience tend to make blanket judgements/recommendations). ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm .Xdefaults & font size
Pál Csányi <[EMAIL PROTECTED]> wrote: > I edit the .Xdefaults : > xterm.*faceName: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* xterm.*font: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* (the package description for biznet font says it is a bitmap font) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] . .. .
Re: xterm .Xdefaults & font size
Pál Csányi <[EMAIL PROTECTED]> wrote: > I edit the .Xdefaults : > xterm.*faceName: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* xterm.*font: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* (the package description for biznet font says it is a bitmap font) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] . .
Re: xterm .Xdefaults & font size
Pál Csányi <[EMAIL PROTECTED]> wrote: > I edit the .Xdefaults : > xterm.*faceName: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* xterm.*font: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* (the package description for biznet font says it is a bitmap font) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] .
Re: xterm .Xdefaults & font size
Pál Csányi <[EMAIL PROTECTED]> wrote: > I edit the .Xdefaults : > xterm.*faceName: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* xterm.*font: -biznet-fixed-*-*-*-*-24-*-*-*-*-*-*-* (the package description for biznet font says it is a bitmap font) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how get colour mutt when ssh from OBSD?
Douglas A. Tutty <[EMAIL PROTECTED]> wrote: > Hello, > I have a box that runs OpenBSD that sshes into my Debian box. On > OpenBSD, the default colour term is vt220 so when I ssh to debian, TERM > is set to vt220. vt220's don't do color. OpenBSD console is normally set to make $TERM to "vt200", which is twice a bug since it doesn't emulate vt220 either (except if one considers that a subset of a vt100 is again a subset of a vt220). > When I run mc, all is well; colour, line draw, whatever. That's a different bug ;-) > When I run lynx or mutt, I get black on white with no colour. On Lynx > this means that my blue on gray ends up as white on black; with mutt I > don't get the blue top and bottom lines or the red thread lines. That's normal... > If I ssh in from an xterm, with TERM=xterm, everything is fine. That's because Debian's "xterm" entry is set to correspond to xterm, which does color. > Does anyone have any clues on this? Conventional applications (excluding hardcoded stuff like GNU ls) uses terminfo/termcap data to determine what the terminal can do. You should report a bug in the applications that don't. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm won't start
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > I've had a pty-related error with xterm on PowerPC in the past. I had > to use the following workaround in my app-defaults file for XTerm: I don't think it is related (it's a different error code). > ! On ay (PPC), ones needs to set eightBitInput to true to avoid the error > ! "xterm: fatal pty error 23 (errno=22) on tty /dev/pts/...". Therefore > ! metaSendsEscape needs to be set to true, to allow non-ASCII characters. > *metaSendsEscape: true > *eightBitInput: true I addressed this in Patch #201 - 2005/4/21 - XFree86 4.5.99.2 * ignore error in the I/O initialization that tries to set the tty to 7-bit input for the case where eightBitInput resource is false (Debian #298551). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: less, exit but left content on screen
Bob Proulx <[EMAIL PROTECTED]> wrote: > I wanted to describe the control-mouse alternate screen switching > capability because it is useful to know about and can help people > understand what is happening at a better level of detail. People who > have never heard of the alternate screen buffer often believe the > screen data is simply gone. Being able to flip back and forth to it > shows where it is and that it is still available. It provides a > better understanding of what is happening under the hood. That's essentially why I added the feature - so I could see what actually happened to the text on the alternate screen. If it were something one would use all the time, it would be worth spending time to popup a window showing the data... > In my experience there are three types of people with regards to this > issue. 1) People who like the alternate screen buffer. 2) People who > don't like the alternate screen buffer. 3) People who sometimes like > it and sometimes don't like it. :-) Therefore I think that for the > people who don't like the behavior that they should simply disable > it. They are probably never going to like it. But it is configurable > in the personal environment so just configure it. right - noting that it's not _always_ possible, it's nice to not have the design choices hardcoded. (and if I do change some feature, it should be not difficult for the user to change it back ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: less, exit but left content on screen
Ralph Katz <[EMAIL PROTECTED]> wrote: > Curious! I haven't had xterm installed now for some time, so I'm going > from memory. Main reason I chose aterm was for the smaller footprint. > At the moment I have 2 aterms running that would suggest more than > scrollback buffer size are factors in RSS: right - there are several factors (some are easy to reproduce, others may for instance depend on the history of the process). fwiw, I was also running xterm compiled for the toolbar, so that would increase xterm's runtime by some amount. > $ ps aux |grep aterm > ralph 2899 0.0 0.9 5956 2360 ?S08:05 0:00 aterm > -tn xterm -sl 5000 -geometry +0-25 > ralph 2900 0.0 0.9 5956 2412 ?S08:05 0:00 aterm > -tr -trsb -rv -sl 100 -sh 95 -geometry +700-350 -e tail -f /var/log/auth.log > ralph 3064 0.0 0.2 1956 640 pts/1R+ 08:10 0:00 grep aterm > $ > Anyway, this is OT (my fault), so did aterm solve your original question > about leaving output from 'less' onscreen after exiting? ...not _my_ original question (the OP's question was answered in effect by noting that it's a detail of the terminal description rather than the terminal emulator). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: less, exit but left content on screen
Ralph Katz <[EMAIL PROTECTED]> wrote: > aterm is also a very nice replacement to xterm because it uses so little > memory. (The 3 aterm windows I have up right now show RSS of 2404, > 2448, and 2464 in output from ps aux.) There are several variables. For instance, the scrollback size affects the RSS. To see the effect, I started "aterm -sl 24", "xterm -sl 24". This is what I saw (for just those two processes, of course): F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 0 1001 6494 6493 15 0 9744 3040 - S+ pts/1 0:00 aterm -sl 24 0 1001 6516 6515 15 0 5788 2852 - S+ pts/1 0:00 xterm -sl 24 -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: less, exit but left content on screen
On Sat, Aug 11, 2007 at 10:40:11PM +0200, Bob Proulx wrote: > Using the standard xterm the control-middle mouse button will display > many options of which one is "Show Alternate Screen". It is possible > to flip back and forth (inconveniently) to see this manually switch to > the alternate screen buffer. ...what would you regard as a convenient way to flip back/forth? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpWEWjE6hT3X.pgp Description: PGP signature
Re: xterm hanging
pol <[EMAIL PROTECTED]> wrote: > Launching /usr/X11R6/bin/xterm from a terminal yields the following lines: > > Warning: translation table syntax error: Unknown keysym name: XF86Paste > Warning: ... found while parsing ' > XF86Paste:insert-selection(SELECT, CUT_BUFFER0) ' > Warning: String to TranslationTable conversion encountered errors > xterm window cannot accept any input. Any ideas? see ftp://invisible-island.net/temp/xterm-226b.patch.gz -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm hanging
pol <[EMAIL PROTECTED]> wrote: > Launching /usr/X11R6/bin/xterm from a terminal yields the following lines: odd - that moved to /usr/bin last year. Is this from the updated Debian package? > Warning: translation table syntax error: Unknown keysym name: XF86Paste > Warning: ... found while parsing ' > XF86Paste:insert-selection(SELECT, CUT_BUFFER0) ' > Warning: String to TranslationTable conversion encountered errors > xterm window cannot accept any input. Any ideas? oops - see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422521 It's an optional compile-time feature, so the packager could disable it. I'll look into a less failure-prone way to supply the feature... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm fonts - problem solved and able to replicate
Deboo ^ <[EMAIL PROTECTED]> wrote: > I was trying some bigger fonts to use with xterm but adding them and > then starting xterm would make xterm size very large, more than the > screen size. So I edited .Xresources and added a xterm*geometry option > to a reasonable geometry size. http://invisible-island.net/xterm/xterm.faq.html#tiny_menus -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Really slow xterm
cothrige <[EMAIL PROTECTED]> wrote: > * Thomas Dickey ([EMAIL PROTECTED]) wrote: >> cothrige <[EMAIL PROTECTED]> wrote: >> > Actually, it has been worse at times than even above. Yesterday, I >> > ran the same test and it took 20 seconds. I thought that was pretty >> > awful. >> >> But at the same time rxvt would be running slower (due to your system load) >> since it's based on the load presented. > No, actually rxvt still ran as usual, and mrxvt a bit quicker still. > I would naturally expect both to be a bit quicker than xterm, but I > don't recall it ever being so obvious as it seems now. While rxvt > seems pretty normal, regardless of the load, xterm always scrolls the > text so slowly that it is very, very obvious. I used to use > xterm quite often, and it just never looked and acted this way. It > actually reminds me of using a framebuffer console in how it is > working right now. huh. Occasionally I see comments regarding X servers and "very slow". But nothing that I've seen first hand. The two issues that I've seen and measured are (1) XCopyArea function and (2) xterm's scrolling area stored as one big chunk which is shifted. The XCopyArea problem occurs for "any" scrolling size on the local host while the big-chunk is a problem for "large" chunks. A couple of years ago, there was a third - which comes back now/then as defects are added/removed in the 2.6 kernels (the sched_yield function is used to work around this, but _that_ has been broken 2-3 times ;-). >> On the other hand, running xterm remotely, I've measured rxvt running 5 times >> slower than xterm. >> >> (though why someone realistically would do "ls -l /usr/bin" hasn't been said) > Well, the situation is that when I am using xterm the screen is > drawing and outputting very slowly. Very visibly so. I ran 'time ls > /usr/bin' simply as a test for the speed of the terminal emulators. > Since that directory was large I figured that I would get the best > most informative results by doing that. scrolling is one place to measure, but there are several (font choice is another, e.g., Xft is notoriously slow). Older versions of rxvt would stop refreshing while they were getting input, and then paint the final screen (usually faster, but with some drawbacks). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Really slow xterm
cothrige <[EMAIL PROTECTED]> wrote: > * Michelle Konzack ([EMAIL PROTECTED]) wrote: >> Am 2007-05-16 15:59:10, schrieb cothrige: >> > I have installed xterm via apt, running etch, and have noticed that it >> > scrolls really slowly. I compared it to rxvt by running `time ls` in >> > /usr/bin with rxvt taking 0.572s and xterm running at 4.633s. Earlier >> > it was even worse taking over 10 seconds. It is a very big difference >> >> It seems, there is somethong wrong with WOUR XTerm. > Actually, it has been worse at times than even above. Yesterday, I > ran the same test and it took 20 seconds. I thought that was pretty > awful. But at the same time rxvt would be running slower (due to your system load) since it's based on the load presented. On the other hand, running xterm remotely, I've measured rxvt running 5 times slower than xterm. (though why someone realistically would do "ls -l /usr/bin" hasn't been said) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm fonts
Deboo ^ <[EMAIL PROTECTED]> wrote: > On 5/23/07, cga2000 <[EMAIL PROTECTED]> wrote: >> If you can't get the menu bar .. you could alway do a Ctrl+mouse button >> (right, left, middle) to bring up xterm menus. > Menubar? In an xterm? Well, atleast I am knowledgeless about this if > it's possible. I have always used the Ctrl-left/middle/right mouse It's a compile-time option (useful, but has some limitations when resizing the window - I use it most of the time). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Really slow xterm
Vincent Lefevre <[EMAIL PROTECTED]> wrote:
> On 2007-05-17 11:03:57 -0000, Thomas Dickey wrote:
>> For "large" scrollbacks, e.g., more than 10,000 lines,
>> xterm has its own problems.
> Hmm... yes. I've tried with xterm using a 20,000-line scrollback,
> and zsh:
> for i in {1..3}; echo $i
> On my 400 Mhz PowerBook G4, Debian/testing, XTerm 225: 71 seconds
> (but only 6 seconds with a 600-line scrollback).
> With rxvt (and a 20,000-line scrollback): 17 seconds.
That contrast looks about right - for an xterm running on the same machine
as the server (which is the most common case for Linux users). It's
an ugly slice of code to rewrite in xterm, but is fixable (preferably
_not_ when I'm trying to fix urgent bugs ;-).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Really slow xterm
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > On 2007-05-16 15:59:10 -0500, cothrige wrote: >> I have installed xterm via apt, running etch, and have noticed that it >> scrolls really slowly. I compared it to rxvt by running `time ls` in >> /usr/bin with rxvt taking 0.572s and xterm running at 4.633s. Earlier given those times, it sounds like the XCopyArea issue. >> it was even worse taking over 10 seconds. It is a very big difference >> in usage, and if I am compiling something it can have very significant >> impact. >> >> Has anybody else had this experience? > xterm has always been very fast here. It depends. There are several issues. For normal/small scrollback sizes, the dominant one is that the XCopyArea function performs far worse on a local connection than on a remote connection. That's a defect in the X libraries (there's no excuse for a _local_ connection to run 15 times slower than the same code running remotely). rxvt happens to not use this defective function (actually it's ifdef'd in the code with a misleading comment regarding the issue). For "large" scrollbacks, e.g., more than 10,000 lines, xterm has its own problems. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Since chvt works, the problem must be the keymap [SOLVED]
Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > that's not good. THat means X is ignoring those keystrokes and passing > them through to Xterm. Fortunately, "X" ignores keystrokes, so you're able to use your keyboard. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Since chvt works, the problem must be the keymap [SOLVED]
Amy Templeton <[EMAIL PROTECTED]> wrote: >> and press CTRL+ALT+F1? > Well...if I do that while I'm still in the XTerm, I see... > ^[[1;7P > ...but I think that's just XTerm freaking out. When another frame > is focused and I press the buttons, there is no output. It helps to read the documentation - http://invisible-island.net/xterm/ctlseqs/ctlseqs.html -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: TERM for small bw monitor?
Kevin Mark <[EMAIL PROTECTED]> wrote: > There is someone who reads this list by the name of Thomas Dickey who > seems to maintain the Xterm package, I suspect that he could provide an > answer. Actually I maintain the xterm program (and others), but no packages. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: TERM for small bw monitor?
Douglas Allan Tutty <[EMAIL PROTECTED]> wrote: > On Wed, Apr 11, 2007 at 11:45:36PM +1000, Paul Dwerryhouse wrote: >> >> On Wed, Apr 11, 2007 at 08:47:35AM -0400, Douglas Allan Tutty wrote: >> > Short of working out a setterm recipe, does anyone know of a TERM >> > setting I can uses that only does white, bright-white, and black? If >> > I use TERM=dumb, I only get white and black and no curses. >> >> Does TERM=vt100 help any? > No. vt100 does colour so its not (any?) different than TERM=linux. no. vt100 never did color (unless you count "black" and "white", which varied according to the phosphor used). Some terminal emulators add the ANSI/ISO controls for colors. But they're not vt100's. > Does anyone remember the name/number of an actual terminal that only did > regular/bright on black? vt100 (noting that the "vt100" terminal description refers to a real hardware terminal that required padding, one may want to suppress the padding, e.g., "man ncurses" and see the comment regarding NCURSES_NO_PADDING). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: web browser choices
Douglas Allan Tutty <[EMAIL PROTECTED]> wrote: > On Tue, Mar 20, 2007 at 02:01:30AM -0400, Celejar wrote: >> On Mon, 19 Mar 2007 17:03:33 -0600 >> "Javier Vasquez" <[EMAIL PROTECTED]> wrote: >> >> [snip] >> >> > I'm sure you'll get better and more pertinent replies, even for the >> > opera vs firefox never ending war. If you'd like to have java They're only pertinent if they mention both programs in an unbiased manner. That's rare on a newsgroup posting, unfortunately (ditto webpages ;-). >> > support, https, and occasionally flash, then I don't see lynx, links, >> > dillo, etc, supporting any of that. Hopefully I'm wrong... As I >> >> You're in luck - you're wrong about links :); it supports https. ditto lynx, w3m. > Somethings I've found interesting when comparing browsers: It seems that > only Lynx supports viewing a gzip file eg README.gz. Only Lynx and Actually w3m does that too (also .bz2, .Z files like lynx ;-). The (e)links(2) flavors do some of that stuff (not as much as lynx(*)). (*) well lynx doesn't do samba urls, so it didn't get noticed on bugtraq recently... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: accented chars. shown as question marks in non-browser tools, sarge
Arlie Stephens <[EMAIL PROTECTED]> wrote: > Sarge and etch offer two packages containing xterm - one of which > calls itself something like XTERM(unicode), except not quite that. Perhaps you're thinking of rxvt-unicode (which is not xterm). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: accented chars. shown as question marks in non-browser tools, sarge
H.S. <[EMAIL PROTECTED]> wrote: > I was helping a friend setup his system with Indic fonts with unicode > support some time ago (a few months). We couldn't get it working in > xterm but it was a breeze to get gnome-terminal and konsole working with Reading your comment closely, it appears that you were probably trying to get xterm to use a specific set of TrueType fonts, but having problems deciding how to specify the font (using the -fa option is the usual issue). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: accented chars. shown as question marks in non-browser tools, sarge
H.S. <[EMAIL PROTECTED]> wrote: > Thomas Dickey wrote: >> H.S. <[EMAIL PROTECTED]> wrote: >>> Arlie Stephens wrote: >> >>>> I've got the same basic problem with just about every tool I use, >>>> notably my email client mutt. Other versions of linux have somehow >> >>> Do you use mutt in xterm? If so, it will be very difficult to get this >>> right. Try this: >> >> yawn (it requires reading the manpage, or using the uxterm script). > I was helping a friend setup his system with Indic fonts with unicode > support some time ago (a few months). We couldn't get it working in > xterm but it was a breeze to get gnome-terminal and konsole working with > Indic fonts under UTF-8 locale. I recall at that time reading someplace that's a datapoint (pango's still incomplete, but it does try). > that UTF-8 support for unicode is not complete in xterm. But I would > sure like to be corrected ... even would be glad since I use xterm on a > daily basis, especially when I am logged in remotely to my univ. machine. >> xterm supports ANSI color, VT220 emulation and UTF-8 >> There's an faq at >> http://invisible-island.net/xterm/xterm.faq.html > I guess I am missing something here, the above page has no occurrence of > UTF in it. making it easier: http://invisible-island.net/xterm/xterm.log.html -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: accented chars. shown as question marks in non-browser tools, sarge
H.S. <[EMAIL PROTECTED]> wrote: > Finally, open gnome-terminal or konsole and fire up mutt. You should see > various language characters in all their glory. BTW, xterm does not > support UTF-8 properly yet. that, or you're not reading the manpage. (hint: provide a useful bug report) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: accented chars. shown as question marks in non-browser tools, sarge
H.S. <[EMAIL PROTECTED]> wrote: > Arlie Stephens wrote: >> >> I've got the same basic problem with just about every tool I use, >> notably my email client mutt. Other versions of linux have somehow > Do you use mutt in xterm? If so, it will be very difficult to get this > right. Try this: yawn (it requires reading the manpage, or using the uxterm script). xterm supports ANSI color, VT220 emulation and UTF-8 There's an faq at http://invisible-island.net/xterm/xterm.faq.html ftp://invisible-island.net/xterm/ -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: best terminal emulator for emacs -nw?
Gnu_Raiz <[EMAIL PROTECTED]> wrote: >>From: Tyler Smith <[EMAIL PROTECTED]> > Wrote one day while in band camp: >> I'm trying to get emacs setup for mutt and slrn. It works really well, >> except for one thing. When I use it as my editor with emacs -nw, the >> alt- key combos get muddled by xterm en route to emacs, so that I have >> to use ESC instead. Is this unavoidable, or is there a terminal >> emulator that allows for the use of meta keys? > I assume you know about gnus right? Some would say that using slrn, and > mutt with emacs is heresy! some people seem to like the color scheme (mutt and tin with ncurses here, editing with vile ;-) > You might want to try the emacswiki it has some good knowledge, if your > really up for some abuse try the emacs irc channel on freenode. Most will > probably point you to the wiki, and laugh unless you find a kind soul who > will help you. But your probably going to get a lot of questions about > the "proper way to use gnus". This might be what your looking for! > http://www.emacswiki.org/cgi-bin/wiki/XtermExtras That looks like enough for him to start on. Even _newer_ xterm can do more. Perhaps some Emacs user will make a package using xterm's modifyOtherKeys escape sequence - see notes starting here: http://invisible-island.net/xterm/xterm.log.html#xterm_216 Anyway - he shouldn't _have_ to use ESC (with xterm). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multi-gnome-terminal alternative
Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: >> A good place to start learning would be by reading bug reports for >> gnome-terminal (some are older than your cited experience, but each >> release of gnome-terminal produces new and interesting bugs). > Interesting. I guess the word regression doesn't mean much to the GNOME > devs? googling on "gnome regression" does show a lot of interesting comments, but I don't see any that give me a different impression. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multi-gnome-terminal alternative
Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: > On Tue, Jan 02, 2007 at 12:19:34AM -0000, Thomas Dickey wrote: >> It appears you didn't read the whole thread (one's mentioned ;-). > I did. Jerome's single problem was mentioned in a reply to a reply to > Marc's message. Marc never provided why he thought it wasn't any good. http://lists-archives.org/debian-user/2322968-multi-gnome-terminal-alternative.html -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multi-gnome-terminal alternative
Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: > I'd be ineterested to learn more. I have been using gnome-terminal > nearly every day since I started using Debian in late 2002. I have had > very few issues with gnome-terminal. >From what I read on google, you're an end-user of gnome-terminal, and don't have any experience writing portable applications that use terminals. End users have a different perspective: it's colorful, etc. We don't argue about that. A good place to start learning would be by reading bug reports for gnome-terminal (some are older than your cited experience, but each release of gnome-terminal produces new and interesting bugs). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multi-gnome-terminal alternative
Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: > Naturally, since he provided *zero* substantiation for his position (if > you could even call it that), I asked if he had in fact used it. Now, I > don't consider that bouncing email around. He did not provide a single > point why gnome-terminal was unsuitable, so I'd like to see at least > one. It appears you didn't read the whole thread (one's mentioned ;-). > BTW, I never claimed that gnome-terminal was a even a passable clone of > xterm. Jerome wanted a possible substitude for multi-gnome-terminal. I > figured the killer feature for him was multiple terminals, thus I > recommended gnome-terminal. >> (Your webpage doesn't work very well with Opera ;-) >>=20 > Care to provide a screenshot? I test in Opera on Mac OS X and Linux > and it looks no different than in Firefox. (Opera 8.52) ftp://invisible-island.net/temp/MenuProblem.png -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: multi-gnome-terminal alternative
Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: > --C7zPtVaVf+AK4Oqc > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > On Sun, Dec 31, 2006 at 04:57:19PM -0800, Marc Wilson wrote: >> On Sun, Dec 31, 2006 at 03:32:26PM -0500, Roberto C. Sanchez wrote: >> > Why not just use gnome-terminal? >>=20 >> Have you ever *used* gnome-terminal? 'Nuff said. >>=20 > Sure. I use it every day even though I am a WindowMaker user. I wish > there was a convenient way to use it on Mac OS X. It is my favorite > terminal program. > Have *you* ever used it? He stated that he had. Perhaps when your reading comprehension improves a little beyond bouncing email around, you will enlighten us on why gnome-terminal is really doing a _good_ job as a clone of xterm. (Your webpage doesn't work very well with Opera ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lynx on Etch ( Ready ? )
[EMAIL PROTECTED] wrote: > Thank you for that. In the mean time I found the answer to my last > question: how to get unicode keyboard input on a console as user: > kbd_mode -u > > I just tried this: create a file in lynx with a name with accented > characters: works. But bookmarked it does not show correctly. But maybe > that is not what you talk about. That could be an analogous issue, but not the same. Older lynx's didn't specify the charset in the header of the bookmark file. It does now, but a quick check seems to show it's using the display charset for that (perhaps not what one would want). > Anyway, I can go ahead for the moment. > Thanks again // Jasper. no problem -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lynx on Etch ( next step )
[EMAIL PROTECTED] wrote: >>>[EMAIL PROTECTED] wrote: >>> >>> >>Lynx (-cur) on Etch: I don't get any characters with accents ! They are >>left out and then another character might get lost as well, for instance >>on the bottom of google.com there is a copyright-sign and then '2006', >>which results in '206'. > Got that one: o for options, Display Charset: Unicode( utf-8 ). It's > there, I previously overlooked it. > Then the next option: Assumed document characterset: can also be set to > utf-8. Also see the option "Use locale-based character set", which (when set) overrides the Display Charset, and can be a little less cumbersome to make lynx display as expected in xterm (non-UTF-8) and uxterm (UTF-8). However - lynx doesn't accept _keyboard_ input in UTF-8 (something that I'd like to do - between fixing bugs ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lynx versus Links2 ( was: Lynx on Etch )
[EMAIL PROTECTED] wrote: > Links2 is probably much better at rendering webpages, tables, frames, > css, even java-script is seems to do. In terms of the original posting however - I just checked to see if it had changed - links2 (like links, elinks), doesn't have a way to display UTF-8. It does have 7-bit approximations (copied from lynx ;-). I seem to recall some recent bug reports for elinks that hint that the developers are working on that (though the nature of the reports makes it plain that it's far from usable). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lynx on Etch
[EMAIL PROTECTED] wrote: > On Sat, Dec 23, 2006 at 02:34:14AM +0100, Jasper wrote: >> >> Both are version 2.8.5 rel.1 . The one at my ISP gives messages in >> english, the one here in dutch. In a console it is the same problem. >> >> Any hints ? >> >> In a way I suspect it is not a lynx problem, because I saw similar >> things in the installer. Could it have to do with the translations of >> messages into dutch ??? > My guess in inconsistent UTF-8 support. I've seen similar things in > aptitude. Try lynx-cur (which is based on the current release of lynx, rather than the previous one from early 2004). The current version of lynx is 2.8.6 It's available at http://lynx.isc.org/lynx2.8.6/ 2.8.7 Development & patches: http://lynx.isc.org/current/index.html -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg , xfree86?
Florian Kulzer <[EMAIL PROTECTED]> wrote: > On Mon, Nov 06, 2006 at 16:24:04 -0000, Thomas Dickey wrote: >> Florian Kulzer wrote: >> >> > for developers to contribute. Someone can make such a statement without >> > being an aspiring contributor himself. I see neither a "promise" nor a >> > "lie" in what he writes. >> >> The lie was this: stating that it was not allowed to happen. > There is no justification for calling someone a liar unless you can > prove that they intentionally spread false information. hmm - the alternative is to prove that he's stupid and spreading other people's false information. Take your pick. >> Anytime the topic came up, invariably it was from people who were not >> going to do the work, but wanted someone else to do it for them. > The wikipedia page on XFree86 certainly suggests that people willing to don't use that as a reference - parts of it are true, but only part. Furthermore, as a reference for this issue, it doesn't address it. > contribute were denied CVS access. If you think you know better what > really happened then you should maybe correct this article and cite > sources to back you up. shrug: the parts that are untrue can easily be checked on mailing list archives. The people who wrote the wikipedia article don't care for that - the _primary_ source of information for appears to be slashdot. > The point of my last mail was that nothing in Kevin's messages in this > thread justifies your borderline rude behavior. He is not responsible > for whatever grudges you have against other people who may or may not > have promised to contribute to XFree86. He's free to followup by actually reporting facts rather than lies. (Given the nature of this mailing list, I'm assuming someone will point out that this is not his _responsibility_). bye -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg , xfree86?
Florian Kulzer <[EMAIL PROTECTED]> wrote: > for developers to contribute. Someone can make such a statement without > being an aspiring contributor himself. I see neither a "promise" nor a > "lie" in what he writes. The lie was this: stating that it was not allowed to happen. Anytime the topic came up, invariably it was from people who were not going to do the work, but wanted someone else to do it for them. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg , xfree86?
Kevin Mark <[EMAIL PROTECTED]> wrote: > On Sun, Nov 05, 2006 at 11:03:01PM +0000, Thomas Dickey wrote: >> Kevin Mark <[EMAIL PROTECTED]> wrote: >> > One of the reasons why there was not a modularized source tree in >> > XFree86 was that it was not allowed to happen. No? So XFree86 never >> > could have it, while Xorg now does. And this lead to XFree86 development >> > being harder than Xorg. To me this is a differnce, a major difference, >> > regardless which version of Xorg has it. >> oh. Then we'll expect to see some significant X development from _you_ in >> the near future, demonstrating that your comment was informed. > Hehe. Only on a free software list could someone ask an individual > to backup their opinion by producing improvements to a mammoth project > like Xorg/Freedesktop :-) The best I can do is send some pennies to the X = > strike not in the least. I noted your comment, and could only interpret it in one of two ways (a lie such as we often see on slashdot, or a promise that since now that things were being done the way you wanted, you'd start to produce something). looking forward to your contribution... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xorg , xfree86?
Kevin Mark <[EMAIL PROTECTED]> wrote: > One of the reasons why there was not a modularized source tree in > XFree86 was that it was not allowed to happen. No? So XFree86 never > could have it, while Xorg now does. And this lead to XFree86 development > being harder than Xorg. To me this is a differnce, a major difference, > regardless which version of Xorg has it. oh. Then we'll expect to see some significant X development from _you_ in the near future, demonstrating that your comment was informed. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm, mutt, emacs -nw, and utf-8
Anders Lennartsson <[EMAIL PROTECTED]> wrote: > Thomas Dickey <[EMAIL PROTECTED]> wrote: >> Presumably you're using the options for telling xterm to use UTF-8 encoding >> as well. But I don't see any details of that here, so it could be a problem. > For xterm I use the default settings for sid|etch|sarge, no local > changes for my user. That's supposed to work (since the "locale" resource would make xterm detect the UTF-8 locale, and start that way). I seem to recall that there's some pitfall. (I usually use uxterm to set the locale per-shell, so I don't have to ferret out places in /etc to make non-UTF-8 locales work for hosts such as this one). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm, mutt, emacs -nw, and utf-8
Anders Lennartsson <[EMAIL PROTECTED]> wrote: > XTERM > Xterm by itself also seems to be able, and if I set the use of fonts > in .Xdefaults by e.g. > XTerm*font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1 > it can print most characters. For example the results of echo -e > "'\303\204\304\211\320\257'". (All shamelessly stolen from pages found > with google.) Presumably you're using the options for telling xterm to use UTF-8 encoding as well. But I don't see any details of that here, so it could be a problem. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: window manager not picking up Xresources?
Mumia W. <[EMAIL PROTECTED]> wrote: > What are those hard-coded commands you're talking about? That's > important because terminal emulators recognize their resources based > upon their names. So if you define resources for "XTerm" (note the > capitals), but you start the program as "xterm," it won't work. no (see the X manpage's discussion of resources). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to tail w/o folding the output?
Ron Johnson <[EMAIL PROTECTED]> wrote: > Hugo Vanwoerkom wrote: >> How do you run tail and not have it fold the output? > Since these apps treat the screen as a "glass teletype", that would > be a function of the console or xterm, not of tail. > As to how to modify the console, though... man console_codes (noting that "DECAWM" refers to a vt100 control sequence) ESC [ ? 7 h DECAWM (default on): Set autowrap on. In this mode, a graphic character emitted after column 80 (or column 132 of DECCOLM is on) forces a wrap to the beginning of the following line first. man xterm -aw This option indicates that auto-wraparound should be allowed. This allows the cursor to automatically wrap to the beginning of the next line when when it is at the rightmost position of a line and text is output. +aw This option indicates that auto-wraparound should not be allowed. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: make menuconfig segfault
Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: > Hi, > Back in 2003 make menuconfig always segfaulted unless I used a ncurses > tarball and used that: > http://lists.debian.org/debian-user/2003/12/msg04950.html > Now, 3 years later, it still happens: ...and still (google says I commented in Sun, Feb 6 2005 11:20 am), the only way to proceed is to run menuconfig with a debugger. I guess it's harder now - the more recent versions have lxdialog loaded as part of another program - but still doable. valgrind and ltrace also would be useful here... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OS X Terminal.app and Aptitude
Ian Brandt <[EMAIL PROTECTED]> wrote: > Thomas Dickey wrote: >>> - Horizontal borders in Aptitude (e.g. in the search or quit >>> dialogs) become '?' characters. >> >> This is more interesting. Those dashes look like they're double-width. I >> have >> a hunch that your locale on Debian is set to a UTF-8 flavor and that aptitude >> is emitting line-drawing in UTF-8, but that Terminal isn't doing the Right >> Thing with that. A quick check with uxterm shows me that aptitude sends >> _something_ in UTF-8. >> >> I seem to recall reading that Terminal can handle UTF-8, so given that, one >> of >> these possibilities comes to mind: >> >> a) the OS X locale isn't UTF-8 (and Terminal gets confused) > I checked my Terminal settings and the encoding is set to UTF-8. I > tried changing my Terminal font from Bitstream Vera Sans Mono to the > included VT-100 and Courier fonts to see if it could be a bug in the > font, but no change. hmm - but the line-drawing characters were all double-width when drawn with UTF-8. tack doesn't know about UTF-8 (yet), and will send just the strings that are in the terminfo. ncurses is sending the UTF-8 strings to work with terminals that require that. I suspect that if you set your locale to en_US then the lines would be drawn properly. Terminal may simply be drawing the lines without using a font (which is what xterm can do), since many fonts do not contain line-drawing characters. >> b) Terminal works for UTF-8 text, but not line-drawing (chooses >> an incorrect set of glyphs for mapping the line-drawing text). > Is one of the terminfo settings related to how double byte characters > are sent to the terminal? Feeling my way around tack I found the > alternate character set tests. Sure enough when set to nsterm many of > the characters are rendered as '?'. Set to our running macosx copy of > OS X's included /usr/share/terminfo/78/xterm-color I see that all the > alternate characters are drawn correctly. That's acsc, enacs, rmacs and smacs. I didn't notice before, but nsterm's acsc string does look odd. Several of the console emulators (Linux, FreeBSD for instance) have mappings that use existing fonts to obtain line-drawing characters from character codes that are always available in the 128-255 range. Looks like nsterm was designed for that. vt100-style mapping uses the enacs, smacs and rmacs strings to initialize and switch to/from an alternate character set that's not always available by a direct mapping. Anyway, nsterm's acsc string is odd since it doesn't seem to match the other ones I'm familiar with. > During that process I also noticed that blink worked when I was set to > nsterm, so I've added 'enter_blink_mode=\E[5m' to macosx with success. > I'm starting to get more familiar with tack, and I see that the > solution here is to get a proper terminfo definition made and > disseminated for Terminal.app. A couple questions related to that quest: > Many tests say a capability is "...not present" or "...not defined". > Examples... > (flash) Flash is not defined. (flash) Done > (cnorm) Cursor-normal is not defined. (cnorm) Done > (hs) Has-status line is not defined. (hs) Done > Would the advisable strategy be to enable these in the terminfo and > see if Terminal.app will then pass the tests? Finding that it To do that, you have to have an idea what string might be recognized. For flash flash=\E[?5h\E[?5l, or flash=\E[?5h$<100/>\E[?5l, might work. The usual problem with flash on different terminal emulators is that they don't honor the delay time. For cnorm, the most common ones use the vt320 sequences cvvis=\E[?25h, cnorm=\E[?25h, Status line is harder - very few terminal emulators do this (aside from the kludges that map title-string escapes onto the terminfo, which don't follow the expected pattern). > supports blink makes me wonder what other capabilities it might > support, though not having comprehensive knowledge of the individual > capabilities themselves I don't know whether you necessarily want them > defined just because Terminal supports them. It would be interesting to read Terminal's source - but I suppose that's part of the code that Apple doesn't publish. > Also, since the menu issues in Aptitude are my only known remaining > bug, any guidance on particular tests/capability settings that might > relate to the rendering issues in the screen shots I posted? A lot of > the drawing and alignment related tests seemed to pass, so nothing is > jumping out at me. I'd focus on the locale - thinking that Terminal's not going to handle UTF-8 properly. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OS X Terminal.app and Aptitude
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > I meant recompiling ncurses, to get version 5.5. But I wonder if Apple > modified the ncurses 5.4, because tic didn't behave like under Debian. > For instance, xterm-* were installed under the 78 subdirectory instead > of the x subdirectory. hex 0x78 is 'x'. I assumed that it was a fix to make the directory-names work around the case-insensitivity of the filesystem. (It's a nuisance, but there are two entries that collide in that case). That wouldn't fix the general case for collisions though since it only addresses the first character. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OS X Terminal.app and Aptitude
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > On 2006-07-11 23:49:23 -0000, Thomas Dickey wrote: >> Vincent Lefevre <[EMAIL PROTECTED]> wrote: >> > Note: you shouldn't use the ncurses that come with Mac OS X. They are >> > buggy. >> >> hmm - to the best of my knowledge, the "ncurses that come with Mac OS X" >> are some version of ncurses, just like Debian/stable, Debian/testing, etc. > This is version 5.4. Recompiling ncurses 5.5 (and Mutt) fixes the > problem. I don't know if it was specific to Mac OS X. ncurses 5.5 was released last fall, so "recompiling" is not a good choice of words. Other people installed ncurses 5.5 on Mac OS X. ncurses 5.4 was released at the beginning of 2004. Advising OP to not use ncurses on Mac OS X is like telling someone not to use a program because Debian/stable has an older/less-capable version. But I recall that you've done this before, so I'll have to disregard similar comments from you in the future. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OS X Terminal.app and Aptitude
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > You should set TERM to 'macosx'. If things don't work, just fix them > in the terminfo data and rerun tic. that's more/less what I was advising. > Note: you shouldn't use the ncurses that come with Mac OS X. They are > buggy. hmm - to the best of my knowledge, the "ncurses that come with Mac OS X" are some version of ncurses, just like Debian/stable, Debian/testing, etc. While I recall a handful of platform-specific bugs, there's no reason why he can't use the terminfo, etc. Are you concerned with a specific bug, or is this just a suggestion to use Linux instead? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OS X Terminal.app and Aptitude
Ian Brandt <[EMAIL PROTECTED]> wrote: > Sorry, meant for this to go to the list (why no Reply-To?)... tin doesn't post to email (I often followup with the same information) > Thomas Dickey wrote: > First off thank you for such a helpful response! >>> "pretty garbled" could be more than one thing... > Here are some screen shots: > <http://www.flickr.com/photos/[EMAIL PROTECTED]/sets/72157594195837848/> >>> Backing up a little, I'd edit that line to show >>> >>> macosx|generic color xterm, >>> >>> and remove the $HOME/.terminfo/x/xterm-color and >>> $HOME/.terminfo/n/nxterm, >>> rerun tic. Then >>> >>> infocmp macosx xterm-color >>> >>> would show whatever changes were made other than the sgr string. > Here is the result: > $ infocmp macosx xterm-color > comparing macosx to xterm-color. > comparing booleans. > comparing numbers. > comparing strings. > hts: '\EH', NULL. > is2: '\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4l\E8\E>', > '\E[m\E[?7h\E[4l\E>\E7\E[r\E[?1;3;4;6l\E8'. > kdch1: '\E[3~', '\177'. > kend: NULL, '\E[4~'. > kfnd: '\E[1~', NULL. > khome: NULL, '\E[1~'. > kslt: '\E[4~', NULL. > meml: NULL, '\El'. > memu: NULL, '\Em'. > rs2: '\E7\E[r\E8\E[m\E[?7h\E[?1;3;4;6l\E[4l\E>', > '\E[m\E[?7h\E[4l\E>\E7\E[r\E[?1;3;4;6l\E8'. ok. Much of this is benign. Note that is2 and rs2 are for instance just altered order. The macosx flavor is older. khome/kend and kfnd/kslt are again an older choice (modeled on vt220) versus the newer preference. kdch1 is like backspace/delete one of the troublesome things, since it's not the "backspace" key but the "Delete" key on the small editing keypad. screen will do odd things if it has the same string as kbs. >>> xterm-color is almost certainly technically incorrect because it's >>> unlikely that Terminal was designed to match that set of data. > I agree. >>> Running on Debian, you should be able to use tack (part of ncurses) >>> to step through the features. I'd expect some differences on the >>> color model for instance. Seeing the test fail for either flavor >>> of "xterm-color" should help a little. > I'll try to learn my way around tack's tests and follow up with a > meaningful log. >>> Since xterm-color was not designed to match Terminal, any >>> differences here aren't going to be applied to ncurses. (In >>> articular, I recall some complaints that the backspace/delete >>> settings don't match Debian). But it would be useful to have an >>> accurate terminal description for Terminal. >>> >>> Supposedly we already have this - the nsterm entries that have >>> been in ncurses since 2001. There were some minor fixes to those >>> early this year - see >>> >>> ftp://invisible-island.net/ncurses/terminfo.src.gz > I compiled your terminfo on my Debian box, and ssh'd over with TERM > set to 'nsterm'. A few initial observations: > - Color is lost at the Bash prompt. bash on Debian? odd - since I thought it would be using ncurses (actually the termcap interface). It may be special-casing $TERM by comparing for something containing "xterm". > - Horizontal borders in Aptitude (e.g. in the search or quit > dialogs) become '?' characters. This is more interesting. Those dashes look like they're double-width. I have a hunch that your locale on Debian is set to a UTF-8 flavor and that aptitude is emitting line-drawing in UTF-8, but that Terminal isn't doing the Right Thing with that. A quick check with uxterm shows me that aptitude sends _something_ in UTF-8. I seem to recall reading that Terminal can handle UTF-8, so given that, one of these possibilities comes to mind: a) the OS X locale isn't UTF-8 (and Terminal gets confused) b) Terminal works for UTF-8 text, but not line-drawing (chooses an incorrect set of glyphs for mapping the line-drawing text). > - Delete works at the bash prompt, but in Aptitude it prints '^[[3~'. > - Backspace works in Aptitude, whereas with xterm-color it printed '^?'. Your stty settings might not match the nsterm terminfo entry. Bear in mind that for *BSD the general rule is stty erase \^H while Debian does stty erase \^? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OS X Terminal.app and Aptitude
Ian Brandt <[EMAIL PROTECTED]> wrote: > Hi, > I'm trying to get OS X 10.4.7's Terminal.app to play nice when ssh'ing > into my Debian Etch box. > I've run `infocmp -L > xterm-color' on my Mac (I have Terminal.app set > to report xterm-color), and compiled the result on my Debian box with > the following output... > $ tic -svx xterm-color > "xterm-color", line 2, terminal 'xterm-color': missing sgr string > 1 entries written to /home/ibrandt/.terminfo > This fixed up my backspace/delete issues at the Bash shell, but when I > try to run Aptitude no such luck. I get ^? when trying to backspace > during a package search, and the menus are pretty garbled. "pretty garbled" could be more than one thing... > Any advice on a next step? I'm completely rusty with all this > terminal emulation voodoo. hmm - since the Mac OS X developers don't write terminal descriptions either, you're on a par with them. > P.S. Here's the infocmp result from the Mac in case that is any help... yes: it answers one of my own questions - whether the Mac OS X developers had constructed a custom terminal description which matched Terminal's functionality - appears the answer is no - aside from removing the sgr (set_attributes) string - no technically sound reason for _that_. > $ cat xterm-color > # Reconstructed via infocmp from file: > /usr/share/terminfo/78/xterm-color > xterm-color|nxterm|generic color xterm, Backing up a little, I'd edit that line to show macosx|generic color xterm, and remove the $HOME/.terminfo/x/xterm-color and $HOME/.terminfo/n/nxterm, rerun tic. Then infocmp macosx xterm-color would show whatever changes were made other than the sgr string. xterm-color is almost certainly technically incorrect because it's unlikely that Terminal was designed to match that set of data. Running on Debian, you should be able to use tack (part of ncurses) to step through the features. I'd expect some differences on the color model for instance. Seeing the test fail for either flavor of "xterm-color" should help a little. Since xterm-color was not designed to match Terminal, any differences here aren't going to be applied to ncurses. (In particular, I recall some complaints that the backspace/delete settings don't match Debian). But it would be useful to have an accurate terminal description for Terminal. Supposedly we already have this - the nsterm entries that have been in ncurses since 2001. There were some minor fixes to those early this year - see ftp://invisible-island.net/ncurses/terminfo.src.gz -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bitstream Vera size in XTerm
Kumar Appaiah <[EMAIL PROTECTED]> wrote: > On 16/06/06, cga2000 <[EMAIL PROTECTED]> wrote: >> Ctrl+ displays xterm's "VT Fonts" menu. > That doesn't work for TrueType fonts in XTerm. It switches to "fixed" > ot something. no - If you've set the -fa option for a valid font, xterm displays in that TrueType font. Selecting default, huge, etc., from the VT Fonts menu makes xterm request a different size for the TrueType font. There's a checkbox on xterm's VT Fonts menu which can be used to turn the TrueType font off/on. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Paste with translation table into gnome-terminal?
Carl Fink <[EMAIL PROTECTED]> wrote: > As I posted to this list a while back, I have had to abandon xterm in favor > of gnome-terminal because some aspect of the xorg upgrade made the xterm > font unchangeable. oh. Which bug report is that? (Debian has a bug-reporting system, which doesn't seem to read random news groups). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dialog package with mouse support
Kevin Mark <[EMAIL PROTECTED]> wrote: > On Sat, May 13, 2006 at 01:34:13PM -0000, Thomas Dickey wrote: >> whiptail doesn't appear to support gpm (only a subset of xterm mouse). > Hi, > have you investigated twin and libtw0. Its curses based and supports a > mouse but I think it maybe dead upstream. I built a copy when it first came out, and at least one followup release, also do recall seeing a Debian package for it (installed it), but haven't had much to do with it otherwise. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dialog package with mouse support
Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: > Thomas Dickey wrote: >> Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: >> >>> Installed libctk-3.0.25. The debian package doesn't work but the tarball >>> does: is the *console tool kit*. No longer supported though and no docs >>> at all. Is supposed to be a console API interface to gtk. Has sound support. >> >> I don't recall noticing this one before. Here's some commentary on it: >> >> http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/45570 >> >> (summary: Linux-specific, no documentation, unsupported...) >> > I am into libctk. I changed the headers to that you can invoke it from > C++. It is neat code! Written by Kevin Lindsay and Wesley Terpstra when > they were working for Stormix which went bellyup in 2001. > Neat idea guys! > Was orphaned in oct 2003: > http://www.debian.org/News/weekly/2003/42/ That means it was dead upstream a while before... > The idea is supreme: a console interface to gtk. You can use anything > gtk API but it runs on the console. > It has not a scrap of docs or man. The examples show up some bugs and I > haven't figured out why yet. > Neither can I get the deb to run. I installed the tar and that runs. > There is no doubt that this is what Debian *should have* instead of why? - Debian should use working code, not an orphaned, undocumented demo. ( otoh, if you feel strongly enough about it, you can finish it ;-) > dialog, if it weren't for the bugs. You should really be able to use a > mouse when using make menuconfig, which uses a stripped version of dialog. no - lxdialog is actually a fork (which has been hacked at by several programmers without finding a suitable maintainer). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dialog package with mouse support
Magnus Therning <[EMAIL PROTECTED]> wrote: > --SO98HVl1bnMOfKZd > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > On Fri, May 05, 2006 at 12:17:19PM -0500, Hugo Vanwoerkom wrote: >>Magnus Therning wrote: >>>On Fri, May 05, 2006 at 06:50:41AM -0500, Hugo Vanwoerkom wrote: Hi, Anybody knows of a dialog package version (Displays user-friendly dialog boxes from shell scripts) that has mouse support? >>>Maybe zenity fits? >>>/M >> >>Well, I'd like to stay out of X. I found something called Ndialog that >>supports the mouse. > Ah, that was an important requirement missing form your original email > :-) > Another option maybe? whiptail whiptail doesn't appear to support gpm (only a subset of xterm mouse). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dialog package with mouse support
Michelle Konzack <[EMAIL PROTECTED]> wrote: > Am 2006-05-05 06:50:41, schrieb Hugo Vanwoerkom: >> Hi, >> >> Anybody knows of a dialog package version (Displays user-friendly dialog >> boxes from shell scripts) that has mouse support? > Yes, "dialog". I was realy surprised as I was able > to klick around under sarge with my mouse. It works > on the console and under X with a XTerm. yes, it's supposed to work, since ncurses 5.5 provides a gpm interface which works around packaging problems with gpm. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dialog package with mouse support
Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: > Installed libctk-3.0.25. The debian package doesn't work but the tarball > does: is the *console tool kit*. No longer supported though and no docs > at all. Is supposed to be a console API interface to gtk. Has sound support. I don't recall noticing this one before. Here's some commentary on it: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/45570 (summary: Linux-specific, no documentation, unsupported...) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dialog package with mouse support
Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: > Well, I'd like to stay out of X. I found something called Ndialog that > supports the mouse. It's interesting, but whenever I've run its demos, it doesn't take long to get a core dump. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xorg upgrade: xdm fails, xterm can't change fonts?
Shawn Lamson <[EMAIL PROTECTED]> wrote: > but it seems from an strace of xterm that /etc/X11/app-defaults/XTerm-color > is no longer checked... I looked through the last 30 days of package > changelogs and didn't see this noted... bug report time? If so, that would be against the X libraries, rather than xterm. The X libraries determine the search path, subject to your environment variables and resource-settings. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: environment for viewing/creating ANSI art?
Andrew Cady <[EMAIL PROTECTED]> wrote: > The "dosemu" package includes the font that you want -- the very same > one that came on the IBM-PC, with all the line-drawing glyphs and such. vga iirc, there's only one small size for it though (fine if you're used to running X in 640x800 mode, but not useful for general purposes). > The other problem is colors. I know that the 'rxvt' xterm clone allows > each ANSI color to be set to an arbitrary RGB value using X resources. hmm - yes: it implements the control sequences that xterm does. (regarding repainting - ymmv). > I don't know what the proper settings are, but I would not be surprised > if the dosemu documentation was helpful in this respect. Unfortunately, > rxvt does not support blinking. xterm does xterm supports ANSI color, VT220 emulation and UTF-8 There's an faq at http://invisible-island.net/xterm/xterm.faq.html ftp://invisible-island.net/xterm/ -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: environment for viewing/creating ANSI art?
John Hasler <[EMAIL PROTECTED]> wrote: > If you want to use the console, 'man consolechars'. 'apropos console' for > other relevant commands. console_codes But its description of character sets is so vague that it could be deleted without losing information. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
