[Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
At some point gnome-terminal changed its strings for modified function-keys. I documented those in terminfo.src for ncurses 5.7 (they don't match xterm, of course). -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259139] Re: Ncurses package does not contain libtinfo
The entrypoints for libinfo are part of ncurses (whether the ncurses library is installed as the two files is a decision made by the packager, and does not affect the ability of applications to use those entrypoints). Any build script which looks explicitly for libtinfo without first trying in the ncurses library should be fixed. -- Ncurses package does not contain libtinfo https://bugs.launchpad.net/bugs/259139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187866] Re: 'tput cols' give strange results
It's expected behavior - in the "80" case, stdout is redirected, so it's no longer a terminal. When this happens, the terminal initialization falls back to the terminfo settings. -- 'tput cols' give strange results https://bugs.launchpad.net/bugs/187866 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 76618] Re: Contents LD_LIBRARY_PATH cleared by xterm
On Sun, 10 May 2009, SimonX200 wrote: > The problem is solved by removing the s-flags from xterm. Why the hack > does a user application like xterm s-flags in the first place? xterm could be installed (and configured...) for systems that use setuid, setgid. setuid is rarely used now (was mainly for pre-Unix98 ptys). setgid is generally used to provide utmp access for systems without the utempter library. (even when utempter is used, some packagers have odd environments that confuse the configure script). > -- > Contents LD_LIBRARY_PATH cleared by xterm > https://bugs.launchpad.net/bugs/76618 > You received this bug notification because you are a direct subscriber > of the bug. > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Contents LD_LIBRARY_PATH cleared by xterm https://bugs.launchpad.net/bugs/76618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
On Fri, 25 Jul 2008, Izzy wrote: > Just wanted to report that the problem disappeared for me after a dist- > upgrade to Hardy (via Gutsy, of course). So maybe the bug is silently > solved? No bug here - it's either a fix in gnome-terminal, or the application using it, e.g., vim. > > -- > [feisty] function keys don't work in gnome-terminal > https://bugs.launchpad.net/bugs/96676 > You received this bug notification because you are a direct subscriber > of the bug. > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 230919] Re: Xterm fails character sets test in vttest
On Fri, 29 Aug 2008, Wouter van Heyst wrote: > According to the changelog for version 236 of xterm, this bug should be > fixed in that version. Doesn't seem to be in Debian yet unfortunately. yes (I don't recall seeing it updated yet in Debian - checked the package page and it's not there). > > -- > Xterm fails character sets test in vttest > https://bugs.launchpad.net/bugs/230919 > You received this bug notification because you are a direct subscriber > of the bug. > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Xterm fails character sets test in vttest https://bugs.launchpad.net/bugs/230919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 230919] Re: Xterm fails character sets test in vttest
On Fri, 29 Aug 2008, Julien Cristau wrote: > On Fri, Aug 29, 2008 at 15:47:00 -0000, Thomas Dickey wrote: > >> On Fri, 29 Aug 2008, Wouter van Heyst wrote: >> >>> According to the changelog for version 236 of xterm, this bug should be >>> fixed in that version. Doesn't seem to be in Debian yet unfortunately. >> >> yes (I don't recall seeing it updated yet in Debian - checked the >> package page and it's not there). >> > I'll try to get to it soon, but since we're frozen for release at the > moment, this hasn't been a priority. hmm (it has been a month, and dialog - more recent - is updated). thanks -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Xterm fails character sets test in vttest https://bugs.launchpad.net/bugs/230919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 230919] Re: Xterm fails character sets test in vttest
On Tue, 9 Sep 2008, Julien Cristau wrote: > On Fri, Aug 29, 2008 at 16:46:40 -, Julien Cristau wrote: > >> On Fri, Aug 29, 2008 at 15:47:00 -0000, Thomas Dickey wrote: >> >>> On Fri, 29 Aug 2008, Wouter van Heyst wrote: >>> >>>> According to the changelog for version 236 of xterm, this bug should be >>>> fixed in that version. Doesn't seem to be in Debian yet unfortunately. >>> >>> yes (I don't recall seeing it updated yet in Debian - checked the >>> package page and it's not there). >>> >> I'll try to get to it soon, but since we're frozen for release at the >> moment, this hasn't been a priority. >> > Uploaded now, sorry for the delay. thanks (report bugs) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Xterm fails character sets test in vttest https://bugs.launchpad.net/bugs/230919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 408496] [NEW] set XTerm*utf8Title to true
On Mon, 3 Aug 2009, Imre Péntek wrote: > Public bug reported: > > by default XTerm*utf8Title is set to false, however the byte sequences > that will change the title bar are actually sent out in utf8, so I > suggest to hard-wire this setting to true. Check the attached screenshot > also. Thank you. > > ** Affects: xterm (Ubuntu) > Importance: Undecided > Status: New sadly, the proper choice depends on the window manager (and probably other factors). I left the default to match existing practice for that reason. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- set XTerm*utf8Title to true https://bugs.launchpad.net/bugs/408496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 407153] Re: ANSI codes for saving/restoring attributes not supported
For the record, the vtansi.htm page (originally by Robert M. Free - though I don't see his name on that copy) contains several technical errors - citing it in a bug report is a nonstarter. In this instance, it happens to say something which is relevant, but still not completely true. In particular, CSI s and CSI u are not vt100 sequences, but xterm happens to recognize them - because it also recognizes several sequences from ISO 6429 - this one since 1996. Saving/restoring attributes on the other hand, is a feature described in technical manuals available at vt100.net - a source with which the vte developers appear to be unfamiliar. -- ANSI codes for saving/restoring attributes not supported https://bugs.launchpad.net/bugs/407153 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 408496] Re: set XTerm*utf8Title to true
On Mon, 3 Aug 2009, Imre Péntek wrote: > Hello, the Ubuntu system generally is utf8 based. That 'Zenék' directory was > created by the installer (when I created my user account), and it really > means Music. So changing the setting I suggest you to change would only mean > that XTerm wouldn't be an exception anymore. I encounter the current > behaviour as an inconsistency (well, any window manager not using utf8 as the > default encoding is also an inconsistency) > again: > i...@most:~$ echo $LANG > hu_HU.UTF-8 > > -- > set XTerm*utf8Title to true If I change a default setting, it's different from having the Ubuntu packager change it... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- set XTerm*utf8Title to true https://bugs.launchpad.net/bugs/408496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 408496] Re: set XTerm*utf8Title to true
On Tue, 4 Aug 2009, Imre Péntek wrote: > Well, I reported an Ubuntu bug: > Where did you find the bug?: > Distribution: Ubuntu > package xterm I maintain xterm upstream, and check bugs in various packages, since as a rule, packagers do not bother to notify upstream. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- set XTerm*utf8Title to true https://bugs.launchpad.net/bugs/408496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69724] Re: Mawk does not support Posix character classes in expressions
One problem with the patch is that it's hardcoded, doesn't use the locale information. I've written an alternate form which is in the 20090727 version of mawk at http://invisible-island.net/mawk/ -- Mawk does not support Posix character classes in expressions https://bugs.launchpad.net/bugs/69724 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321890] Re: hex print in mawk does not work on ubuntu 64bit
It doesn't appear to be related to 64-bits. The values correspond to the first character of the parameters. Incidentally, mawk's behavior matches awk's (perhaps gawk's behavior is an extension). -- hex print in mawk does not work on ubuntu 64bit https://bugs.launchpad.net/bugs/321890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355883] Re: Jaunty: CTRL-LEFT and CTRL-RIGHT do not work in zsh
Regarding comment #11 and following - xterm is configurable. I suggest that he read the documentation and customize it. (This is not even a wishlist item, since it's a problem with the user's understanding of the program). -- Jaunty: CTRL-LEFT and CTRL-RIGHT do not work in zsh https://bugs.launchpad.net/bugs/355883 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364474] Re: Jaunty: no icon in the title menu of xterm
The xterm source package provides suitable icons, which the Ubuntu packager could install. -- Jaunty: no icon in the title menu of xterm https://bugs.launchpad.net/bugs/364474 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378668] Re: Cursor in terminal behaves badly with special characters present
>From the description, it sounds as if the problem is in bash. -- Cursor in terminal behaves badly with special characters present https://bugs.launchpad.net/bugs/378668 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320958] Re: xterm renders some unicode characters incorrectly when using colors (or bold?)
Whether a character shows up as a box or not depends on whether the font contains the given glyph. xterm has separate normal/bold font settings, and (though it can be configured to use overstriking rather than a bold font) will choose to use the bold font for bold text. By the way, on my Debian/testing "ls --color" doesn't show those names colored. That's 7.4-2 -- xterm renders some unicode characters incorrectly when using colors (or bold?) https://bugs.launchpad.net/bugs/320958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 355883] Re: Jaunty: CTRL-LEFT and CTRL-RIGHT do not work in zsh
On Thu, 30 Jul 2009, Bernhard wrote: > @Thomas: I have since configured my terminal via shell settings. The > desired behaviour should be default though, especially for "out-of-the- > box" Ubuntu. Doing that would break existing applications (those that use the terminal description from ncurses and xterm, for example), and would introduce sequences which correspond to those already sent by other combinations. (It's likely that some other users of Ubuntu would object to this). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Jaunty: CTRL-LEFT and CTRL-RIGHT do not work in zsh https://bugs.launchpad.net/bugs/355883 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355883] Re: Jaunty: CTRL-LEFT and CTRL-RIGHT do not work in zsh
Near the end of this section, there's a table showing the codes sent by xterm for different modifiers: http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#PC-Style Function Keys Back to the original report - A "3" is sent for an "alt" key, a "5" for a control key. That's not changed in upstream xterm, isn't likely to. But the report says a "3" is sent with a control key. However, gnome-terminal has changed several times. None of this is documented except in bug reports. For instance, at one point gnome-terminal set its keys based on a termcap entry. That didn't work well since the termcap entry lacked information on the control/cursor-keys. As I recall, they "fixed" the problem by hardcoding in some behavior. But in doing so, they neglected to bother to make it compatible. The (unresolved) problems with gnome-terminal are technically solvable. For instance, xterm has an option (-kt tcap) which tells it to read the "termcap". But if it is linked with ncurses, it reads the extended information that describes these keys. (If the terminfo doesn't describe the key, xterm's free to use its builtin behavior of course). -- Jaunty: CTRL-LEFT and CTRL-RIGHT do not work in zsh https://bugs.launchpad.net/bugs/355883 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 26603] Re: String indexes are inconsistent with other awks
no - as Aharon Robbins pointed out (and X/Open): substr(s, m[, n ]) Return the at most n-character substring of s that begins at position m, numbering from 1. If n is omitted, or if n specifies more characters than are left in the string, the length of the substring shall be limited by the length of the string s. That's undefined behavior. It would be nice to match behavior in various aspects which aren't documented, and fall outside the standard. But that's a wishlist item rather than a bug. -- String indexes are inconsistent with other awks https://bugs.launchpad.net/bugs/26603 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400409] Re: RS is readonly
mawk does care - but it's not accepting a explicit null-character. I've added a fix for the next snapshot of mawk. -- RS is readonly https://bugs.launchpad.net/bugs/400409 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
On Tue, 23 Oct 2007, Alexey Borzenkov wrote: > Also I just found that xterm sends slightly different codes for > Shift+F1...F4, so this myxterm.ti is also for xterm: > > xterm|X11 terminal emulator with correct kf-sequences, This would be for xterm with modifyFunctionKeys:0 I made a list in xterm (duplicated in ncurses) called "xterm+pcf0". > kf13=\EO1;2P, > kf14=\EO1;2Q, > kf15=\EO1;2R, > kf16=\EO1;2S, and this would be with modifyFunctionKeys:2 The corresponding list is called "xterm+pcf2", and corresponds to the default settings. The terminfo entries are built up in chunks to make it (relatively) simple to patch the terminfo to reflect different preferences for resource-settings. > kf13=\E[1;2P, > kf14=\E[1;2Q, > kf15=\E[1;2R, > kf16=\E[1;2S, > use=xterm-xf86-v44, > > However Shift+F2 acts as Shift+F4 (in mc) in xterm too. refer to ftp://invisible-island.net/ncurses/terminfo.src.gz which lists several of the chunks for xterm (not all combinations - there are many). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
On Tue, 23 Oct 2007, Alexey Borzenkov wrote: > I'd like to second steviant's request. For a long time this bug forced > me to use konsole instead of gnome-terminal, just for ability to press > Shift+F4. Unfortunately with konsole Shift+Left/Shift+Right don't work > (which work under gnome-terminal), so editing text files is not of much > use. It's really annoying that I can get one part of a functionality > with only one terminal and the other half only with other. :-/ It sounds as if someone's trying to use TERM=xterm for all three, which won't work. > I've just downloaded ncurses sources and finally found why Thomas > Dickey's example didn't make sense (and didn't compile). There's no > xterm-xf86-v44. Ubuntu actually uses xterm-debian. So the first attempt terminfo.src change history shows it's been in the sources a while: # 2004-06-26 # * add mlterm -TD # * add xterm-xf86-v44 -TD # * modify xterm-new aka xterm-xfree86 to accommodate luit, which relies # on G1 being used via an ISO-2022 escape sequence (report by # Juliusz Chroboczek) -TD # * add 'hurd' entry -TD # > was like this: > > $ cat >myxterm.ti > xterm|X11 terminal emulator with correct kf-sequences, > kf13=\EO1;2P, > kf14=\EO1;2Q, > kf15=\EO1;2R, > kf16=\EO1;2S, > use=xterm-debian, > ^D > $ tic myxterm.ti > $ mc > > And then I figured that now Shift+F2 acts like Shift+F4. Either Midnight > Commander expects kf14 to be Shift+F4 (which doesn't seem to be correct, > I'll show later why), or something is fishy here. Now I made it like > this: Some packagers prefer to number shifted-f1 to shifted-f12 as F10-F22. Some terminals implement this, some implement F13-F24 (hardcoded). xterm has a resource-setting to select it - ctrlFKeys (class CtrlFKeys) In VT220 keyboard mode (see sunKeyboard resource), specifies the amount by which to shift F1-F12 given a control modifier (CTRL). This allows you to generate key symbols for F10-F20 on a Sun/PC keyboard. The default is ``10'', which means that CTRL F1 generates the key symbol for F11. which I added in 2000. The terminfo entries I maintain for ncurses and xterm reflect the default resource settings. If you want to change the resource settings, you need a new terminfo entry (suggest doing it with a script ;-). > $ cat >myxterm.ti > xterm|X11 terminal emulator with correct kf-sequences, > kf11=\EO1;2P, > kf12=\EO1;2Q, > kf13=\EO1;2R, > kf14=\EO1;2S, > use=xterm-debian, by the way, Debian maintains "xterm-debian" - it won't be in ncurses upstream, nor in xterm upstream. > ^D > $ tic myxterm.ti > $ mc > > Now it works in mc, but it seems extremely, EXTREMELY, wrong to me. > > What do I actually see when I run konsole and try pressing Shift+F1..F4? > > $ cat > ^[O2P^[O2Q^[O2R^[O2S > $ echo $TERM > xterm > > Now, if you look at xterm+pcfkeys in > ncurses-5.6+20070716/debian/xterm.ti you'll see that ^[O2S (Shift+F4) is > mapped to kf16, yet when I press Shift+F4 in Midnight in konsole, it > works correctly! So what's exactly happening? I clearly can't sanely map > kf11...kf14 to be Shift+F1...F4 just for midnight (I assume something > else will likely break then). How do I make Shift+F1...F4 work like they > work in konsole? It sounds as if you want to change xterm's modifyFunctionKeys resource. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
On Tue, 23 Oct 2007, Alexey Borzenkov wrote: > Thomas, I don't seem to understand you. I just grabbed and compiled > terminfo.src you gave and while it helped with xterm (except that it's > just like with my previous attempts, Shift+F2 starts a new file in mc > instead of Shift+F4) it didn't work in gnome-terminal (because of \E[ > and \EO difference I pointed before). However I just recompiled libvte I don't use mc, but have read that it stores key-definitions per $TERM with its learn-keys feature. That may be what's confusing it. Also, recall that I pointed out that some terminals use different numbering for the shift-F1 to F10 or F12. gnome-terminal is a different problem since it hardcodes $TERM to "xterm" and attempts to read function-key definitions from the termcap interface. Note that I said "termcap" - iirc, it's only got one table. This makes it do interesting (buggy) behavior for the shift/control cursor/function keys, since it guesses incorrectly on the cases where they're not in termcap. It does sort-of work for the codes in termcap. (I haven't noticed any mismatches for the common cases of TERM using tack). > with changing "#if 1" to "#if 0" and gnome-terminal now works correctly I'm not sure which "#if 1" you're talking about here. > (Shift+F4 now starts a new file in mc, with original ubuntu terminfo, no > other modifications were needed). The change in the source only affects > addition of "1;" and shouldn't make any difference in regards to > Shift+F2/Shift+F4 (since I didn't change any resources), should it? If > it does then I'm clearly missing something big here and I'd like to know > where I could read what this "1;" actually means at all? you seem to be referring to here to something like \E[1;2A The "1;" is the first parameter in the control sequence. In my first version of function-key modifiers, I did something like \E[2A but after some time someone pointed out that it violated the convention that the cursor key strings could be interpreted the same as the corresponding cursor movement controls. The first parameter for cursor movements is a repeat-count. So I added a dummy parameter "1" to fix that. gnome-terminal and konsole copied the first version, did not adapt the improved version. (xterm provides both, and more via the modifyXXX resources). After some time, gnome-terminal was modified (unsure when - neither GNOME nor KDE developers document things) to read the termcap. So it sort-of works. > > P.S. I'm not affiliated with ubuntu/debian development yet (merely a > "new" user who recently returned back to linux after moving to windows a > decade ago), so I can't even suggest anything going or not going > upstream. I'm just trying to understand what's going on here with this > bug. > > -- > [feisty] function keys don't work in gnome-terminal > https://bugs.launchpad.net/bugs/96676 > You received this bug notification because you are a direct subscriber > of the bug. > > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124254] Re: [gutsy] xterm .desktop file places it in Applications -> System menu
It's up to the packager (just in case someone thought it should go upstream). There are no standards on the menus. -- [gutsy] xterm .desktop file places it in Applications -> System menu https://bugs.launchpad.net/bugs/124254 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 72530] Re: meta key (alt key) combinations don't work in xterm
On Sun, 5 Aug 2007, Timo Aaltonen wrote: > I get M-x on gutsy, could you try if it works for there? > > ** Changed in: xterm (Ubuntu) > Importance: Undecided => Low > Status: Confirmed => Incomplete I don't have gutsy. I maintain xterm, and was pointing out that the resource settings were not strictly necessary. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- meta key (alt key) combinations don't work in xterm https://bugs.launchpad.net/bugs/72530 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128136] Re: uxterm man page has a typo
That file is maintained in Debian (I don't recall if it's licensed so I could incorporate it in xterm). -- uxterm man page has a typo https://bugs.launchpad.net/bugs/128136 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
Agree: gnome-terminal has never emulated all of xterm's control sequences, and it is unlikely that it ever will. That's why there is a separate terminfo entry "gnome" to address its actual behavior. Set $TERM to "gnome" and report discrepancies there. For instance, the comment about gnome's bug #337252 points to a change in xterm 5 years ago. That's not recent. By the way - to get correct information (rather than the miscellany of 2-3 year old secondary sources, you might look at the xterm source itself. gnome-terminal developers do... -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 128136] Re: uxterm man page has a typo
On Sun, 5 Aug 2007, Timo Aaltonen wrote: > and I mean asking the Debian folks.. ok (I don't have it at hand, but will look to see what its status is). I do maintain the uxterm script (though I seem to recall there is a Debian patch for that, which uses a nonportable feature). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- uxterm man page has a typo https://bugs.launchpad.net/bugs/128136 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
On Sun, Aug 05, 2007 at 08:58:45PM -, Izzy wrote: > First it is very funny: Half a year just pointing at each other saying > "There's the problem, not here!". :-( > > @Thomas Dickey goes Second: > ===[ cut here ]=== > [EMAIL PROTECTED]:~$ echo $TERM > gnome > [EMAIL PROTECTED]:~$ mc > Unknown terminal: gnome > Check the TERM environment variable. > Also make sure that the terminal is defined in the terminfo database. > Alternatively, set the TERMCAP environment variable to the desired > termcap entry. hmm - yes. It's a shame about the termcap package - hasn't been maintained for several years. That's using a file that was last updated in March 2000. I added the gnome entry late in 1999 - shortly after ncurses 5.0. Eric Raymond's file is mostly (aside from reordering the entries to assert "creative" input, and changing the version number) a copy of the ncurses 5.0 file with less than 500 lines added. At best it's a nuisance. > [EMAIL PROTECTED]:~$ > ===[ end quote ]=== > So much about setting TERM=gnome - and here's your report. See ftp://invisible-island.net/ncurses/termcap.src.gz for an authentic up-to-date termcap source. (report bugs - but don't waste time with things that were fixed long ago) > Honestly: Does anybody at least know a work-around for this? It's pretty > annoying... Shift-F1 to Shift-F4 are completely unusable - regardless > whether one uses xterm or gnome terminal. Konsole also, even if it > simply "eats" the keystrokes (without displaying anything). ( works for me ;-) -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
On Sun, Aug 05, 2007 at 08:58:45PM -, Izzy wrote:
> gnome
> [EMAIL PROTECTED]:~$ mc
> Unknown terminal: gnome
> Check the TERM environment variable.
> Also make sure that the terminal is defined in the terminfo database.
> Alternatively, set the TERMCAP environment variable to the desired
> termcap entry.
For reference, here's what a current "gnome" looks like in terminfo:
# Reconstructed via infocmp from file:
/usr/local/ncurses/lib/terminfo/g/gnome
gnome|GNOME Terminal,
am, bce, mir, msgr, xenl,
colors#8, cols#80, it#8, lines#24, pairs#64,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, bold=\E[1m, civis=\E[?25l, clear=\E[H\E[2J,
cnorm=\E[?25h, cr=^M, csr=\E[%i%p1%d;%p2%dr,
cub=\E[%p1%dD, cub1=^H, cud=\E[%p1%dB, cud1=^J,
cuf=\E[%p1%dC, cuf1=\E[C, cup=\E[%i%p1%d;%p2%dH,
cuu=\E[%p1%dA, cuu1=\E[A, dch=\E[%p1%dP, dch1=\E[P,
dl=\E[%p1%dM, dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K,
enacs=\E)0, flash=\E[?5h$<100/>\E[?5l, home=\E[H,
hpa=\E[%i%p1%dG, ht=^I, hts=\EH, il=\E[%p1%dL, il1=\E[L,
ind=^J, is2=\E[m\E[?7h\E[4l\E>\E7\E[r\E[?1;3;4;6l\E8,
kDC=\E[3;2~, kLFT=\EO2D, kRIT=\EO2C, kb2=\E[E, kbs=\177,
kcbt=\E[Z, kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA,
kdch1=\E[3~, kend=\EOF, kf1=\EOP, kf10=\E[21~, kf11=\E[23~,
kf12=\E[24~, kf13=\EO2P, kf14=\EO2Q, kf15=\EO2R,
kf16=\EO2S, kf17=\E[15;2~, kf18=\E[17;2~, kf19=\E[18;2~,
kf2=\EOQ, kf20=\E[19;2~, kf21=\E[20;2~, kf22=\E[21;2~,
kf23=\E[23;2~, kf24=\E[24;2~, kf25=\EO5P, kf26=\EO5Q,
kf27=\EO5R, kf28=\EO5S, kf29=\E[15;5~, kf3=\EOR,
kf30=\E[17;5~, kf31=\E[18;5~, kf32=\E[19;5~,
kf33=\E[20;5~, kf34=\E[21;5~, kf35=\E[23;5~,
kf36=\E[24;5~, kf37=\EO6P, kf38=\EO6Q, kf39=\EO6R,
kf4=\EOS, kf40=\EO6S, kf41=\E[15;6~, kf42=\E[17;6~,
kf43=\E[18;6~, kf44=\E[19;6~, kf45=\E[20;6~,
kf46=\E[21;6~, kf47=\E[23;6~, kf48=\E[24;6~, kf49=\EO3P,
kf5=\E[15~, kf50=\EO3Q, kf51=\EO3R, kf52=\EO3S,
kf53=\E[15;3~, kf54=\E[17;3~, kf55=\E[18;3~,
kf56=\E[19;3~, kf57=\E[20;3~, kf58=\E[21;3~,
kf59=\E[23;3~, kf6=\E[17~, kf60=\E[24;3~, kf61=\EO4P,
kf62=\EO4Q, kf63=\EO4R, kf7=\E[18~, kf8=\E[19~, kf9=\E[20~,
kfnd=\E[1~, khome=\EOH, kich1=\E[2~, kmous=\E[M, knp=\E[6~,
kpp=\E[5~, kslt=\E[4~, meml=\El, memu=\Em, op=\E[39;49m,
rc=\E8, rev=\E[7m, ri=\EM, rmacs=^O, rmam=\E[?7l,
rmcup=\E[2J\E[?47l\E8, rmir=\E[4l, rmkx=\E[?1l\E>,
rmso=\E[m, rmul=\E[m, rs1=\Ec,
rs2=\E7\E[r\E8\E[m\E[?7h\E[!p\E[?1;3;4;6l\E[4l\E>\E[?1000l\E[?25h,
sc=\E7, setab=\E[4%p1%dm, setaf=\E[3%p1%dm,
sgr=\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;m%?%p9%t\016%e\017%;,
sgr0=\E[0m\017, smacs=^N, smam=\E[?7h, smcup=\E7\E[?47h,
smir=\E[4h, smkx=\E[?1h\E=, smso=\E[7m, smul=\E[4m,
tbc=\E[3g, u6=\E[%i%d;%dR, u7=\E[6n,
u8=\E[?%[;0123456789]c, u9=\E[c, vpa=\E[%i%p1%dd,
and in termcap - ignoring size limit:
# Reconstructed via infocmp from file:
/usr/local/ncurses/lib/terminfo/g/gnome
gnome|GNOME Terminal:\
:am:bs:mi:ms:ut:xn:\
:Co#8:co#80:it#8:li#24:pa#64:\
:#4=\EO2D:%i=\EO2C:*4=\E[3;2~:*6=\E[4~:@0=\E[1~:@7=\EOF:\
:AB=\E[4%dm:AF=\E[3%dm:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:\
:DO=\E[%dB:F1=\E[23~:F2=\E[24~:F3=\EO2P:F4=\EO2Q:F5=\EO2R:\
:F6=\EO2S:F7=\E[15;2~:F8=\E[17;2~:F9=\E[18;2~:\
:FA=\E[19;2~:FB=\E[20;2~:FC=\E[21;2~:FD=\E[23;2~:\
:FE=\E[24;2~:FF=\EO5P:FG=\EO5Q:FH=\EO5R:FI=\EO5S:\
:FJ=\E[15;5~:FK=\E[17;5~:FL=\E[18;5~:FM=\E[19;5~:\
:FN=\E[20;5~:FO=\E[21;5~:FP=\E[23;5~:FQ=\E[24;5~:\
:FR=\EO6P:FS=\EO6Q:FT=\EO6R:FU=\EO6S:FV=\E[15;6~:\
:FW=\E[17;6~:FX=\E[18;6~:FY=\E[19;6~:FZ=\E[20;6~:\
:Fa=\E[21;6~:Fb=\E[23;6~:Fc=\E[24;6~:Fd=\EO3P:Fe=\EO3Q:\
:Ff=\EO3R:Fg=\EO3S:Fh=\E[15;3~:Fi=\E[17;3~:Fj=\E[18;3~:\
:Fk=\E[19;3~:Fl=\E[20;3~:Fm=\E[21;3~:Fn=\E[23;3~:\
:Fo=\E[24;3~:Fp=\EO4P:Fq=\EO4Q:Fr=\EO4R:K2=\E[E:Km=\E[M:\
:LE=\E[%dD:RA=\E[?7l:RI=\E[%dC:SA=\E[?7h:UP=\E[%dA:\
:ac=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~:\
:ae=^O:al=\E[L:as=^N:bl=^G:cd=\E[J:ce=\E[K:ch=\E[%i%dG:\
:cl=\E[H\E[2J:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:\
:ct=\E[3g:cv=\E[%i%dd:dc=\E[P:dl=\E[M:do=^J:eA=\E)0:\
:ec=\E[%dX:ei=\E[4l:ho=\E[H:im=\E[4h:\
:is=\E[m\E[?7h\E[4l\E>\E7\E[r\E[?1;3;4;6l\E8:k1=\EOP:\
:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\E[15~:k6=\E[17~:k7=\E[18~:\
:k8=\E[19~:k9=\E[20~:k;=\E[21~:kB=\E[Z:kD=\E[3~:kI=\E[2~:\
:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:kh=\EOH:\
:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:md=\E[1m:\
:me=\E[0m:ml=\El:mr=\E[7m:mu=\Em:nd=\E[C:op=\E[39;49m:\
:r1=\Ec:\
:r2=\E7\E[r\E8\E[m\E[?7h\E[!p\E[?1;3;4;6l\E[4l\E>\E[?1000l\E[?25h:\
:rc=\E8:sc=\E7:se=\E[m:sf=^J:
Re: [Bug 128136] uxterm manpage
On Wed, 15 Aug 2007, Julien Cristau wrote: > Hi, > > I fixed the typo in 229-1. thanks > > Thomas, the manpage carries the following licensing information: (on my to-do list - #229 was just to fix some bugs that were distracting me from other work) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- uxterm man page has a typo https://bugs.launchpad.net/bugs/128136 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 96676] Re: [feisty] function keys don't work in gnome-terminal
On Tue, 14 Aug 2007, Izzy wrote: > I just found out that the problem does *NOT* appear with konsole. That's not unexpected, given the history of the feature. I implemented the original flavor in (xterm of course) Patch #94 - 1999/3/27 - XFree86 3.9Pf and made the change which seems to be the root of this discussion in Patch #167 - 2002/8/24 - XFree86 4.2.0 and documented/extended the permutations in Patch #216 - 2006/8/3 Patch #223 - 2006/11/30 iirc, konsole is using the original flavor, while as noted, gnome-terminal attempts to use the terminfo entry but reportedly is not associating things in the same way that I setup for xterm. Aside from unintentionally changing the default for the behavior that corresponds to the modifyCursorKeys resource as noted for #223, I don't _recall_ having changed anything in the terminfo which would be incompatible - for xterm itself. gnome-terminal, of course, is expected to work either way since it reads the terminal description. > Checking a bit deeper, it uses TERM=linux - setting TERM=xterm here > breaks a few things again. The other way round (setting TERM=linux in a > xterm session) is not helpful at all. Side-effect of TERM=linux is that > you lose mouse support (at least as far as Midnight Commander is > affected). So you have the choice of "mouse XOR keyboard working fine". Midnight Commander is probably linked with s-lang, which only looks for "xterm" in $TERM to decide if the terminal supports mouse. ncurses looks at the kmous capability (which is more reliable). btw - the extra key-bindings for alt/shift/control modifiers in the terminfo descriptions are invisible to s-lang, since it has its own terminfo reader... (not really noticeable for Midnight Commander if you're using the learn-keys feature). > @Thomas Dickey: If you could send me the affected termcap files (and say > where they belong to), I would try to replace mine (after a backup). If > that solves the issue, we at least know how to work around the bug until > it's solved (which I guess will not happen that soon - to be honest, I > would even be surprised if it was solved in Gutsy). I'm puzzled by the original description, which states that infocmp is showing \EO rather than \E[ for the control sequence initiator, but am guessing that Ubuntu is still assigning "xterm" to the 5-year-old version of xterm. (While xterm can be configured to match this, that was changed for a good reason, and it would be nice if we didn't have to deal with antique bugs). The way to construct a _terminfo_ entry (I thought Ubuntu is a repackager of Debian...), is to make a text file such as xterm|customized entry, use=xterm-xf86-v44, and compile that with tic (noting that if you're not root, then it may go to $HOME/.terminfo - a bad feature which was depcrecated long ago). See also http://invisible-island.net/ncurses/ncurses.faq.html#unknown_term -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- [feisty] function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52034] Re: multiple xterms not restoring from X session save
compare with http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423961 (I looked to see if any of it can be fixed in xterm, but googling on "metacity xtsessionid" found this). In turn that leads to http://bugzilla.gnome.org/show_bug.cgi?id=341286 So it does not look like xterm. -- multiple xterms not restoring from X session save https://bugs.launchpad.net/bugs/52034 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72530] Re: meta key (alt key) combinations don't work in xterm
If you're going to do all of that, the uxterm script is already designed to set the locale and fonts properly for UTF-8 mode. -- meta key (alt key) combinations don't work in xterm https://launchpad.net/bugs/72530 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76618] Re: Contents LD_LIBRARY_PATH cleared by xterm
Apparently "most" refers to Redhat, using utempter. Otherwise, xterm's installed setgid. The X libraries (as you should have noted, having commented "as often reported") for several years have stripped certain environment variables from setuid and setgid programs. utempter isn't much of an improvement (read it - or gnome-terminal ;-) There's other ways to use the linker than by hacking up your filesystem. Look into rpath, for instance. -- Contents LD_LIBRARY_PATH cleared by xterm https://launchpad.net/bugs/76618 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51982] Re: UK Pound sign key not handled correctly by ncurses
This bug report is completely unrelated to ncurses. -- UK Pound sign key not handled correctly by ncurses https://launchpad.net/bugs/51982 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537616] Re: *** glibc detected *** awk: munmap_chunk(): invalid pointer: 0x000000000061b26c ***
There's more than one issue - gt5 immediately complains that sort does not work if I run it in the default locale (en_US.UTF-8). Setting that to POSIX lets me run it. However, running with karmic's old version of mawk, gt5 does not show colors. But (still POSIX) with current mawk, gt5 does show colors. -- *** glibc detected *** awk: munmap_chunk(): invalid pointer: 0x0061b26c *** https://bugs.launchpad.net/bugs/537616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 519243] Re: [hardy] [mawk] match() works in exponential time even tough the ~ doesn't
This is fixed in current release http://invisible-island.net/mawk/ -- [hardy] [mawk] match() works in exponential time even tough the ~ doesn't https://bugs.launchpad.net/bugs/519243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485574] Re: mawk text-match count inconsistency
This test case does show something (the tokens are being parsed properly, but the comparison is failing). -- mawk text-match count inconsistency https://bugs.launchpad.net/bugs/485574 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 569565] [NEW] ssh regressions in lucid: cursor color, window size info
On Sat, 24 Apr 2010, Akkana Peck wrote: > Public bug reported: > > Binary package hint: xterm > > Since upgrading from karmic to lucid, I'm having the following problems > with xterm: > > 1. Handling of window size isn't passed to remote machines via telnet. > If I telnet to another machine inside our firewall (yes, I know telnet > isn't secure for outside connections), I can't use vim on the remote > machine. The terminal size isn't passed correctly, long lines don't wrap > properly, and window size changes don't get passed through to vim or > other programs such as more. ssh does seem to pass most of this info > correctly. man xterm, see "allowWindowOps" resource. Debian changed the default for this resource setting. > 2. The cursor color resource no longer works: cursor is still black even with > XTerm*cursorColor: red fixed in xterm #257 > If I copy the xterm version from karmic, XTerm(243), and run it, both of > these problems go away. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- ssh regressions in lucid: cursor color, window size info https://bugs.launchpad.net/bugs/569565 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Sat, 8 May 2010, frotz wrote: > On Thu, 6 May 2010, Thomas Dickey wrote: > >>> What's the difference between Debian and Ubuntu to cause Debian's xterm >>> background to be black? Backgrounds are black on Jaunty, but not Karmic >>> and not Lucid. A dirty work-around is to use this command "xterm -class >>> XTerm-color" to spawn an xterm. What can I put in .Xresources to make >>> an xterm always assume that it should use the XTerm-color class? >> >> Debian sets the background color by a modification to >> /etc/X11/app-defaults/XTerm, combined with >> the /etc/X11/Xresources/x11-common file. That's been discussed, pointed >> out where to look > > Looking at the links associated with this bug, I don't see anything > about a resource setting that forces xterm to use XTerm-color as if it > was specified on the command line. setting "*customization:color" does this. That's set in x11-common. For some systems (without that detail), I do the same thing by putting the setting in my $HOME/.Xdefaults; however not all sessions startup using _that_ value. (But for Ubuntu, my understanding is that it should work using the x11-common value - however other comments let me see that KDE has added some additional breakage of X-resources which needs to be explained). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Thu, 6 May 2010, frotz wrote: > What's the difference between Debian and Ubuntu to cause Debian's xterm > background to be black? Backgrounds are black on Jaunty, but not Karmic > and not Lucid. A dirty work-around is to use this command "xterm -class > XTerm-color" to spawn an xterm. What can I put in .Xresources to make > an xterm always assume that it should use the XTerm-color class? Debian sets the background color by a modification to /etc/X11/app-defaults/XTerm, combined with the /etc/X11/Xresources/x11-common file. That's been discussed, pointed out where to look - -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 438850] Re: xterm ignores VT100 widget resources color16 through color255
On Fri, 8 Jan 2010, Bryce Harrington wrote: >> From the last comment, sounds like this is a wontfix issue. Certainly > not something we'd patch ourselves in ubuntu, and upstream already knows > about the issue, so no need to have this bug report open any further. It would only be fixed in the X libraries. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm ignores VT100 widget resources color16 through color255 https://bugs.launchpad.net/bugs/438850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 320958] Re: xterm renders some unicode characters incorrectly when using colors (or bold?)
On Fri, 8 Jan 2010, Bryce Harrington wrote: > Sorry, this testing was on Karmic. I'll check on Lucid in a moment. The fonts are probably much the same... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm renders some unicode characters incorrectly when using colors (or bold?) https://bugs.launchpad.net/bugs/320958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 438850] Re: xterm ignores VT100 widget resources color16 through color255
On Fri, 8 Jan 2010, Bryce Harrington wrote: > Actually, fixing the manpage is probably within scope. The next xterm > upload will fix this. It's been documented in the xterm manpage since patch #250. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm ignores VT100 widget resources color16 through color255 https://bugs.launchpad.net/bugs/438850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Fri, 8 Jan 2010, Bryce Harrington wrote:
> Hmm, not sure how to go about fixing this. I can confirm the behavior.
> We're not doing anything in the xterm packaging to make it white rather
> than black in Ubuntu. Maybe something elsewhere in the system is
> causing it to show up white but I can't tell what that would be. Afaik
> we don't have a preference in Ubuntu whether to have it black or white,
> and are going to just take whatever upstream and debian feel to be the
> best default.
>
> Can anyone confirm that on current versions of debian it is colored
> correctly? If so, then if anyone can spot what in Ubuntu is causing it
I'm always running Debian/testing, and haven't seen the colors go awry.
("xrdb -query" might show a stray resource).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
xterm background colour used to be black, now white
https://bugs.launchpad.net/bugs/421261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-x-swat] [Bug 421261] Re: xterm background colour used to be black, now white
Julian's comment #15 seems to be the best clue (though why it would be set for uxterm and not xterm, I don't know). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Sat, 9 Jan 2010, Bryce Harrington wrote: > Well, I'm out of clue. I don't see where we have anything different > from debian for the Xresources for this. I don't have a ~/.Xdefaults, > and the x11-common resource file is the same as from debian. If I had something like that where I could test it, I'd see if I could use strace to show which files were opened on startup. iirc, a setting from xrdb wouldn't show up in this way, but resource settings would. (For this purpose, xterm runs fine without setgid, in case that interferes). something like strace -tfo foo.out xterm would show that. (I expect it to be large - compressed attachments are nice ;-). Tweaking uxterm to get the same information can be done by editing the last line of the script. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485574] Re: mawk text-match count inconsistency
Unless access_log is encoded in UTF-8 (a possibility), mawk and gawk should give the same result for that pattern. -- mawk text-match count inconsistency https://bugs.launchpad.net/bugs/485574 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505526] Re: xterm word wrap bug
** Changed in: xterm (Ubuntu) Status: New => Invalid -- xterm word wrap bug https://bugs.launchpad.net/bugs/505526 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255322] Re: xterm does not handle tab character in last column correctly
This is the same issue as described in my faq: http://invisible-island.net/xterm/xterm.faq.html#grep_colors (not a bug in xterm) ** Changed in: xterm (Ubuntu) Status: Triaged => Invalid -- xterm does not handle tab character in last column correctly https://bugs.launchpad.net/bugs/255322 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 505526] Re: xterm word wrap bug
On Wed, 20 Jan 2010, Imre Péntek wrote: > May I ask why it is changed to invalid? btw I can still reproduce with > xterm under ubuntu. It's not a bug, but the way vt100's would work. That seems the most appropriate status. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm word wrap bug https://bugs.launchpad.net/bugs/505526 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269895] Re: diffstat: bogus parsing of diffs that contain \ No newline at end of file
This was fixed upstream in http://invisible-island.net/diffstat/CHANGES 31-Aug-2009 diffstat 1.49 add special case for no-newline message from some diff's (Ubuntu #269895). -- diffstat: bogus parsing of diffs that contain \ No newline at end of file https://bugs.launchpad.net/bugs/269895 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209537] Re: diffstat does not honor COLUMNS environment variable
diffstat already has a -w option which can be used to achieve the same result. Making it respond to the environment variable would change existing uses. man diffstat -w number specify the maximum width of the histogram. The histogram will never be shorter than 10 columns, just in case the filenames get too large. -- diffstat does not honor COLUMNS environment variable https://bugs.launchpad.net/bugs/209537 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 481740] Re: termcap emulation broken
This was fixed upstream in 20091114 + limit hashing for termcap-names to 2-characters (Ubuntu #481740). -- termcap emulation broken https://bugs.launchpad.net/bugs/481740 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 481253] Re: xvile 9.7 hangs on amd64 (9.6 was ok)
The fixes mentioned are in 9.7x (which currently is in Lucid). I made one additional fix which may be relevant for 9.7y (the current version is 9.7z, I have unrelated changes for 9.7za) -- xvile 9.7 hangs on amd64 (9.6 was ok) https://bugs.launchpad.net/bugs/481253 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 464274] Re: Karmic libncurses5.7 problems
This was fixed upstream in 20091031 + change initialization of "hidden" flag for soft-keys from true to false, broken in 20090704 merging (Ubuntu #464274). -- Karmic libncurses5.7 problems https://bugs.launchpad.net/bugs/464274 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
Upstream has these changes, last updated in 20091003 > patch by Benjamin C W Sittler: + add linux-16color -- init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000) https://bugs.launchpad.net/bugs/438413 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 209537] Re: diffstat does not honor COLUMNS environment variable
On Wed, 20 Jan 2010, Steve Langasek wrote: > The request was for diffstat to honor the existing $COLUMNS env > variable. Commandline options are orthogonal to this. If you have some advice on how to not impact existing usage, you should comment on that in the bug report. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- diffstat does not honor COLUMNS environment variable https://bugs.launchpad.net/bugs/209537 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96676] Re: function keys don't work in gnome-terminal
I've never come across any useful documentation from the GNOME project. Just stuff that is targeted at nontechnical end-users. However, the simplest fix would be setting gnome-terminal's TERM variable to "gnome", and handling the inevitable release-to-release nits with fixes in the terminal database. -- function keys don't work in gnome-terminal https://bugs.launchpad.net/bugs/96676 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 464783] Re: gnome-terminal should default to 80x25 for application compatibility
The report has several problems. I'll list a few of them. vte would like to emulate xterm (it's incomplete). xterm emulates vt100, vt220, etc. Those are all 24x80. PC's have 25x80. But their emulation of vt100 is weak, with well-known differences. Terminator isn't relevant to the topic. Generally speaking, terminal emulators do not pay much attention to the termcap data. It's useful (as xterm and gnome-terminal can do) to set function keys. For sizing the terminal - the use of that via termcap is an archaic feature. The scrap of termcap in gnome-terminal's source (aside from the fact that an upstream bug notes that the feature is not working) is purely to enable gnome-terminal to find the data (for some reason its developers did not use the conventional terminfo or termcap interfaces to obtain this information). The comment about wikipedia (a) misinterprets what is there and (b) wikipedia is not a reliable source. -- gnome-terminal should default to 80x25 for application compatibility https://bugs.launchpad.net/bugs/464783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 464783] Re: gnome-terminal should default to 80x25 for application compatibility
On Wed, 3 Mar 2010, Dominic Evans wrote: > @dickey so what is your suggested fix for the usability issue? :-) It should be fixed in the qemu package, rather than gnome-terminal (by making it work with different screensizes). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- gnome-terminal should default to 80x25 for application compatibility https://bugs.launchpad.net/bugs/464783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 526894] [NEW] xterm wrongly handles Unicode on the prompt when printing text
On Wed, 24 Feb 2010, Dominik George wrote: > Public bug reported: This appears to be a duplicate of 526893. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm wrongly handles Unicode on the prompt when printing text https://bugs.launchpad.net/bugs/526894 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 526893] [NEW] xterm wrongly handles Unicode on the prompt when printing text
On Wed, 24 Feb 2010, Dominik George wrote: > Public bug reported: > > Binary package hint: xterm > > xterm misinterpretes some characters and writes junk text to the > terminal under the followign conditions: > > 1. The prompt contains special charachters, in this test case german umlauts > 2. The text printed from a command (shell built-in, program, script, etc.) > does not end with a line break Sounds like a problem with one of (a) the user's configuration, or (b) the shell. Not a bug in xterm. > > Steps to reproduce: > > Start xterm or any terminal emulator relying on it (e.g. gnome- > terminal), then create or cd into a directory containing an umlaut (e.g. indeed "any terminal emulator" > LANG=de_DE.UTF-8 > SHELL=/bin/zsh Is this the actual shell? If so, it should be reassigned to that package. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm wrongly handles Unicode on the prompt when printing text https://bugs.launchpad.net/bugs/526893 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526894] Re: xterm wrongly handles Unicode on the prompt when printing text
*** This bug is a duplicate of bug 526893 *** https://bugs.launchpad.net/bugs/526893 ** This bug has been marked a duplicate of bug 526893 xterm wrongly handles Unicode on the prompt when printing text -- xterm wrongly handles Unicode on the prompt when printing text https://bugs.launchpad.net/bugs/526894 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 526893] Re: xterm wrongly handles Unicode on the prompt when printing text
On Wed, 24 Feb 2010, Dominik George wrote: > zsh is the login shell, but this is about Bash (running from zsh or > "native" does not matter). The bug is reproducible across multiple > hosts, users, environments. > > It is not related to the shell itself. The bug can be reproduced in > Bash, Dash and Csh. bash (but not dash or csh as far as I recall) contains code which is supposed to count the length of the prompt, for positioning the cursor. The code in bash has been the subject of occasional bug reports for some time. > The bug does not show when running in a tty, so it *is* X-related. > > ** Also affects: gnome-terminal (Ubuntu) > Importance: Undecided > Status: New gnome-terminal, konsole and xterm all are independent - it's likely that there is a common cause for this issue which is unrelated to any of these. You may get some insight on the problem by using "script" to capture the output of the shell (to see which characters are sent to the terminal). That may be different between the Linux console and the X applications. > > ** Also affects: kdebase (Ubuntu) > Importance: Undecided > Status: New > > -- > xterm wrongly handles Unicode on the prompt when printing text > https://bugs.launchpad.net/bugs/526893 > You received this bug notification because you are subscribed to xterm > in ubuntu. > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm wrongly handles Unicode on the prompt when printing text https://bugs.launchpad.net/bugs/526893 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Tue, 1 Sep 2009, Julien Cristau wrote: > On Sat, Aug 29, 2009 at 23:28:51 -, Gavin McCullagh wrote: > >> gavi...@teenie:~$ xrdb -query >> Xcursor.size: 18 >> Xcursor.theme: Human >> Xcursor.theme_core: true >> Xft.antialias: 1 >> Xft.dpi:96 >> Xft.hinting:1 >> Xft.hintstyle: hintslight >> Xft.lcdfilter: lcddefault >> Xft.rgba: rgb >> >> Not sure I see anything there >> > This is missing '*customization: -color', which should be set by > /etc/X11/Xresources/x11-common. I see - overlooked that. It could have been set in his .Xdefaults, though, which would have shown up in the appres listings. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258089] Re: xterm segfaults when run via panel launcher
The previous comment stated that it was assumed to be fixed in #235. This comment repeats the original report against #229. (The current version is #248). -- xterm segfaults when run via panel launcher https://bugs.launchpad.net/bugs/258089 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258089] Re: xterm segfaults when run via panel launcher
No - since there's no fix released for 8.04 Hardy. But it's certainly not a "New", since there's previous history which tends to make it "Confirmed". (There's no progress on it in this release). -- xterm segfaults when run via panel launcher https://bugs.launchpad.net/bugs/258089 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 311983] Re: Window title, DECRQSS security
On Sat, 12 Dec 2009, David Sharnoff wrote: > xterm can't change it's title any more. Did this fixing this "bug" There is a resource setting that can disable it - perhaps someone set that. (which version of xterm are we discussing?) > break this important feature? The screen program is one example of an > application where changing the title critical. > > Title changes still work with gnome. Only broken with kde. Karmic. I suppose it's possible that xrdb has different data in gnome/kde. (It's simple enough to check - look at the control-right-mouse entry for "Enable Title Ops", which must be enabled to allow this feature). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Window title, DECRQSS security https://bugs.launchpad.net/bugs/311983 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 311983] Re: Window title, DECRQSS security
On Sat, 12 Dec 2009, Paul Szabo wrote: >>> xterm can't change it's title any more. ... >> ... look at the control-right-mouse entry for "Enable Title Ops" ... > > Testing my own karmic machine: the xterm default "Allow Title Ops" is > ticked, "Allow Window Ops" is not ticked. Apparently regardless of allowTitleOps doesn't have an effect on retrieving the title. That's controlled via allowWindowOps: allowTitleOps (class AllowTitleOps) Specifies whether control sequences that modify the window title or icon name should be allowed. The default is "true." allowWindowOps (class AllowWindowOps) Specifies whether extended window control sequences (as used in dtterm) should be allowed. These include several control sequences which manipulate the window size or position, as well as reporting these values and the title or icon name. Each of these can be abused in a script; curiously enough most terminal emulators that implement these restrict only a small part of the repertoire. For fine-tuning, see disallowedWindowOps. The default is "false." (my recent changes in-filled some empty slots in the dtterm list, but did not alter the allowTitleOps feature, since that was separate from dtterm). > setting, using > perl -e 'print "\e\]0;;bad-command;\a\e\[21t"' > does not set the title; but with "Allow Window Ops" ticked, it echoes > the bad command into the input buffer. > > Cheers, Paul > > Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ > School of Mathematics and Statistics University of SydneyAustralia > > -- > Window title, DECRQSS security > https://bugs.launchpad.net/bugs/311983 > You received this bug notification because you are subscribed to xterm > in ubuntu. > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Window title, DECRQSS security https://bugs.launchpad.net/bugs/311983 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 311983] Re: Window title, DECRQSS security
On Sat, 12 Dec 2009, Paul Szabo wrote: > Dear Thomas, > > The "problem" is not with the meanings or descriptions of AllowTitleOps > (though a warning that "setting AllowWindowOps is insecure" is missing). > > The problem is that > perl -e 'print "\e\]0;;bad-command;\a\e\[21t"' > should set the title (then maybe retrieve it); but that setting does not > happen on Ubuntu. (The setting works fine on Debian, and there is no I understood the problem statement, and suggested one of the possibilities, which could be checked by anyone who's able to reproduce the problem. (Another possibility is that he's using patch #243, for which there was already a fix - but bug reports lacking a version number for xterm don't have enough information to do more than speculate). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Window title, DECRQSS security https://bugs.launchpad.net/bugs/311983 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495733] Re: xterm title won't change with kde (xttitle, xtermset, xtermcontrol all broken)
I don't see xterm's version number anywhere, and don't see a pointer to the package definition for xterm, to see what changes may have been made from the upstream source. -- xterm title won't change with kde (xttitle, xtermset, xtermcontrol all broken) https://bugs.launchpad.net/bugs/495733 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495733] Re: xterm title won't change with kde (xttitle, xtermset, xtermcontrol all broken)
If it's the same executable (and unless KDE now has some feature for disabling changes to the titlebar), then it's probably a difference in X resource settings due to starting xrdb with a slightly different set of files. If it's X resources, then you should be able to see the "Allow Title Ops" menu entry unchecked (control/right mouse menu) when running in KDE. -- xterm title won't change with kde (xttitle, xtermset, xtermcontrol all broken) https://bugs.launchpad.net/bugs/495733 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 311983] Re: Window title, DECRQSS security
On Sat, 12 Dec 2009, David Sharnoff wrote: > Sorry, I'm using 243-1ubuntu1 -- the current version in Karmic. thanks (I don't have Ubuntu, so I need information to fill in between upstream source and the package details). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Window title, DECRQSS security https://bugs.launchpad.net/bugs/311983 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495733] Re: xterm title won't change with kde (xttitle, xtermset, xtermcontrol all broken)
It would be greyed out if "Allow SendEvents" (control/left/menu) is enabled (in turn, that could be a resource-difference between GNOME/KDE). man xterm allowSendEvents (class AllowSendEvents) Specifies whether or not synthetic key and button events (gen- erated using the X protocol SendEvent request) should be inter- preted or discarded. The default is "false" meaning they are discarded. Note that allowing such events creates a very large security hole, and forcefully disables the allowXXXOps resources. The default is "false." -- xterm title won't change with kde (xttitle, xtermset, xtermcontrol all broken) https://bugs.launchpad.net/bugs/495733 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320388] Re: accentuated characters wrongly displayed (encoding problem) in title bar
see http://invisible-island.net/xterm/xterm.log.html#xterm_210 man xterm (resource settings): utf8Title (class Utf8Title) Applications can set xterm's title by writing a control sequence. Normally this control sequence follows the VT220 convention, which encodes the string in ISO-8859-1 and allows for an 8-bit string terminator. If xterm is started in a UTF-8 locale, it translates the ISO-8859-1 string to UTF-8 to work with the X libraries which assume the string is UTF-8. However, some users may wish to write a title string encoded in UTF-8. Set this resource to "true" to allow UTF-8 encoded title strings. That cancels the translation to UTF-8, allowing UTF-8 strings to be displayed as is. The default is "false." -- accentuated characters wrongly displayed (encoding problem) in title bar https://bugs.launchpad.net/bugs/320388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 481253] [NEW] xvile 9.7 hangs on amd64 (9.6 was ok)
On Thu, 12 Nov 2009, Joachim Schimpf wrote: > Public bug reported: > > Binary package hint: xvile > > I upgraded from jaunty to karmic, which apparently involved xvile 9.6m-1 > being upgraded to xvile 9.7s-1. > > Start xvile on any file, then type dd, and it hangs and needs to be > killed. > > I went back to xvile 9.6m-1 and everything is fine. reportedly it works with the fixes I've made since 9.7w, e.g., the patch in ftp://invisible-island.net/temp/ (whether it's a compiler- or vile-bug hasn't been isolated; my fixes are largely doing a sanity-check on the results from unsigned/signed conversions). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xvile 9.7 hangs on amd64 (9.6 was ok) https://bugs.launchpad.net/bugs/481253 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Fri, 2 Apr 2010, Gavin McCullagh wrote: > Strangely, today I upgraded to the latest lucid packages and now my > uxterm is white as well. http://invisible-island.net/xterm/xterm.log.html#xterm_256 -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Wed, 19 May 2010, Martin Stolle wrote: > Hi, is anyone working on this? It's really annoying 8-). So far, Ubuntu ranks _last_ of all bug-tracking systems that I deal with, for getting things done. Perhaps the package maintainers tend to assume that all of the work is done in Debian. > I ran uxterm under strace and it appears to only look for UXTerm and > _NOT_ UXTerm-color resources. Since x11-common is responsible for > making it use -color, I looked for uxterm opening that file in the > strace, but it appears to ignore that file. If I manually xrdb > -override that file, it works as expected. > > In conclusion, the root bug seems to be that uxterm does not (or no > longer) consults /etc/X11/Xresources/x11-common Could this be a > regression in Xt? Can this be fixed, maybe? Or is this an unintended > side-effect of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570447 ? It could be similar, but this report is older than #570447 -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 587056] [NEW] vim mapping of fails when connected using putty
On Fri, 28 May 2010, Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug:
>
> Binary package hint: firefox
>
> The mapping I use in vim is
> map a=strftime("%d/%m/%Y %T")
>
> When I use putty to connect to open a console to the system, I open vim and
> F3 prints the date
> When I use putty to connect to the machine, then start "screen", I open vim
> and F3 no longer works.
putty isn't xterm.
There is a "putty" terminal description which matches the default settings
for putty. It is different from xterm.
> I don't attribute the problem to putty though, because I can connect to
> a Redhat 5 system and the mapping works regardless of screen.
>
> The environment variable is "xterm" and "screen" when outside/inside
> screen respectively.
>
> The problem is the same when mapping F2,F3 and F4.
> F5 works okay inside/outside screen.
>
> To confuse things further, when using gnome-terminal the mapping works
> inside and outside screen and TERM values are the same.
gnome-terminal isn't xterm, etc.
(set TERM=gnome, for instance).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
vim mapping of fails when connected using putty and screen
https://bugs.launchpad.net/bugs/587056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 464783] Re: gnome-terminal should default to 80x25 for application compatibility
On Wed, 3 Mar 2010, Anthony Liguori wrote: > You can use an ANSI sequence to resize a terminal. The following works > in gnome-terminal: technically that's not ANSI (other than the form). It's one of the dtterm (Sun) sequences that I implemented for xterm. The security people don't much like it. > echo -en '\033[8;25;80t' && qemu -curses ... > > But it's somewhat impolite to resize a user's terminal automatically > though. :-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- gnome-terminal should default to 80x25 for application compatibility https://bugs.launchpad.net/bugs/464783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421261] Re: xterm background colour used to be black, now white
The only (upstream) thing that comes to mind is to make the include-structure of the uxterm app-defaults files consistent with xterm. Doing that will make this user's windows both have a white background. I'm doing that for patch #256. I did notice that on my Debian/stable (sarge), that the "customization:color" is not set in /etc/X11/Xresources/x11-common (but my $HOME/.Xdefaults had long had the setting). I don't see a followup from Gavin to tell if the setting is missing from his x11-common file. -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438850] Re: xterm ignores VT100 widget resources color16 through color255
Other than documenting it in the manpage as a limitation of the X libraries, there's no fix to be made, noting that it's already documented in the changelog from 5 years ago. -- xterm ignores VT100 widget resources color16 through color255 https://bugs.launchpad.net/bugs/438850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 399625] Re: Merge ncurses 5.7+20090803-1 (main) from Debian unstable (main).
On Tue, 8 Sep 2009, Martin Pitt wrote: > Since it's past feature freeze now, does that new upstream version have > any intrusive changes/new features? Do we need it in karmic to fix > urgent bugs? What's the previous patch-date? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Merge ncurses 5.7+20090803-1 (main) from Debian unstable (main). https://bugs.launchpad.net/bugs/399625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 399625] Re: Merge ncurses 5.7+20090803-1 (main) from Debian unstable (main).
On Tue, 8 Sep 2009, Martin Pitt wrote: > Since it's past feature freeze now, does that new upstream version have > any intrusive changes/new features? Do we need it in karmic to fix > urgent bugs? Reading this bug report, it seems that 20090607 is where karmic is. 20090613 has a build-fix. There are fixes for ongoing changes between 20090613 and 20090803, but I didn't note in http://invisible-island.net/ncurses/NEWS.gz that any of those were due to changes older than 20090613 (the build-fix in 20090613 wasn't complete - there's some followup mentioned for --srcdir in 20090815 and 20090905, however there are other changes which are less stable - backporting of the 2-3 lines affected is a better choice) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Merge ncurses 5.7+20090803-1 (main) from Debian unstable (main). https://bugs.launchpad.net/bugs/399625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190852] Re: Screen missing terminfo entries for 'xterm'
Actually, there was adequate information to discuss the report. (looks like someone's mis-triaging reports). -- Screen missing terminfo entries for 'xterm' https://bugs.launchpad.net/bugs/190852 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 190852] Re: Screen missing terminfo entries for 'xterm'
On Wed, 28 Oct 2009, Kamus wrote: > @Thomas, please what do you mean with mis-triaging? I closed this report > because have a long time here without activity and since nobody has > confirmed this problem I change to invalid until other people can check > if this issue is still occurring. Please remember some paragraphs of > code of conduct my friend. There's enough information to see the basic problem. What's lacking is for the package maintainer to follow the thread, ask questions if they don't follow it. The essential problem reported is that Ubuntu's customization to change kbs (presumably to change it from ^H to \177) did not work for the person who reported the problem. That can be because the screen entries did not contain that customization, or due to an error in one of the special terminfo entries (even a bug in screen ;-). ncurses's terminfo database contains some special entries which are interpreted by screen, e.g., these listed by toe: screen.xterm-xfree86screen customized for modern xterm screen.xterm-r6 screen customized for X11R6 xterm screen.teraterm disable ncv in teraterm screen.rxvt screen in rxvt screen.Etermscreen in Eterm screen.linuxscreen in linux console screen.mlterm screen in mlterm That is, outside 'screen', if $TERM is "mlterm", for instance, it would use "screen.mlterm". Those entries work around various problems with screen's matching _exactly_ a given terminal entry. The followup should have been focused on first verifying what the terminfo entry inside 'screen' was, and what the special entry shows, to see if one of those displays the problem. If they're set properly, then (barring the reporter _wanting_ kbs=^H), then it should have been reassigned back to screen's maintainer to analyze. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Screen missing terminfo entries for 'xterm' https://bugs.launchpad.net/bugs/190852 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 190852] Re: Screen missing terminfo entries for 'xterm'
On Wed, 28 Oct 2009, Micah Cowan wrote: > Kamus, I see absolutely nothing in Thomas Dickey's comments that even > remotely hint at a violation of the Code of Conduct, so maybe you could > consider dialing your sensitivity down a bit? > > Thomas, I think the (previous) "Incomplete" status was due to the > question as to whether it was still reproducible in recent releases; I > don't believe it is (I've never seen any of "screen.xterm", "screen > ..xterm-color" or any other provided on an Ubuntu system, so wouldn't be > able to produce his setup), and the original poster didn't respond in > nearly a year, so that's normally grounds for closing the bug as > "Invalid". I don't have Ubuntu to compare, but my understanding is that it's largely a copy of Debian/testing. Those entries in Debian/testing would be in the larger "ncurses-term" package: /usr/share/terminfo/s/screen.rxvt /usr/share/terminfo/s/screen.xterm-r6 /usr/share/terminfo/s/screen.mlterm /usr/share/terminfo/s/screen.xterm-xfree86 /usr/share/terminfo/s/screen.teraterm /usr/share/terminfo/s/screen.Eterm /usr/share/terminfo/s/screen.linux /usr/share/terminfo/s/screen.xterm-new > FWIW, I'm not sure if Ubuntu's "kbs=\177" value counts as a > "customization"; that's what screen currently provides in its included > terminfo description, and I know Ubuntu(/Debian) include code from > relatively recent development versions. ncurses's terminfo.src has kbs=^H. Since (all but a few) terminfo entries come from ncurses in Debian, etc., the change is addressed by a packager's patch (customization). In particular, the Debian package for 'screen' does not install any terminfo data... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Screen missing terminfo entries for 'xterm' https://bugs.launchpad.net/bugs/190852 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 464274] [NEW] Karmic libncurses5.7 problems
On Fri, 30 Oct 2009, Michael Selig wrote: > Public bug reported: > > Binary package hint: libncurses5 > > Just upgraded to Karmic, and some legacy ncurses programs broke, using > libncurses5 ver 5.7+20090303-2ubuntu2. > Replacing /lib/libncurses.5.7.so with the version from Jaunty fixes the > problems. > > There seem to be 2 separate problems: > > 1) Function key "soft labels" don't appear. That sounds like a regression which I fixed in 20090815 + correct use of terminfo capabilities for initializing soft-keys, broken in 20090509 merging. (iirc, Ubuntu bumped up to 20090803) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Karmic libncurses5.7 problems https://bugs.launchpad.net/bugs/464274 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 438054] [NEW] SCIM and Anthy do not work
On Mon, 28 Sep 2009, juhtolv wrote: > Public bug reported: > > Binary package hint: xterm > > Whenever I want to write Japanese language, I use input method called > Anthy, via scim-bridge. No matter how much I hit Ctrl-Space, Alt-Space > or Shift-Space, SCIM-toolbar do not appear at all, when mouse cursor is > over some xterm. In Gnome-applications it just works. Also using SCIM- > applet in notification area has exactly the same problem: If I choose > Anthy from its popup-menu, Anthy starts working only in Gnome-apps. > > If SCIM-toolbar appears and mouse cursor hovers from Gnome-app to xterm, > that toolbar disappears. It comes back, if mouse cursor hovers over some > Gnome-app. > > Did you forget to enable the support for input methods, when you > compiled xterm? I haven't disabled it - it should work as it did, for some time. Packagers do enable/disable. (more information would help). > > ** Affects: xterm (Ubuntu) > Importance: Undecided > Status: New > > -- > SCIM and Anthy do not work > https://bugs.launchpad.net/bugs/438054 > You received this bug notification because you are subscribed to xterm > in ubuntu. > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- SCIM and Anthy do not work https://bugs.launchpad.net/bugs/438054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438850] Re: xterm ignores VT100 widget resources color16 through color255
Not a bug in xterm, but a limitation of the X libraries. http://invisible-island.net/xterm/xterm.log.html#xterm_188 Patch #188 - 2004/5/12 - XFree86 4.4.99.6 modify initialization of 256- and 88-colors so that colors beyond 16 are normally not X resources. This works around a hard-coded limit in Xt which breaks xterm when 256-colors and luit are both configured (report by Noah Friedman). -- xterm ignores VT100 widget resources color16 through color255 https://bugs.launchpad.net/bugs/438850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400409] Re: RS is readonly
If the Debian packager were responding, it would be about a week. However, he's ignored most of my bug reports (aside from the one about incorrect license). Look here - I've marked fixed-upstream on the ones that I believe are done... http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk -- RS is readonly https://bugs.launchpad.net/bugs/400409 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293708] Re: lynx can't find issuer of some https sites and can't connect with -dump
Is this with lynx 2.8.1dev.1, or some other version? -- lynx can't find issuer of some https sites and can't connect with -dump https://bugs.launchpad.net/bugs/293708 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293708] Re: lynx can't find issuer of some https sites and can't connect with -dump
This isn't the same case as Debian #231609 (I'll make a fix in lynx 2.8.8dev.1). -- lynx can't find issuer of some https sites and can't connect with -dump https://bugs.launchpad.net/bugs/293708 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] [NEW] xterm background colour used to be black, now white
On Sat, 29 Aug 2009, Gavin McCullagh wrote: > Public bug reported: > > Binary package hint: xterm > > Since upgrading my Acer Aspire One to Karmic, my xterms always have a > white background. > > Looking at /etc/X11/app-defaults/XTerm-color, it appears it should be > black: > > ! Set the default text foreground and background colors. > *VT100*foreground: gray90 > *VT100*background: black There's missing information (since this update is likely to be mixed in with other changes): a) what was the previous version of xterm used? b) if you install the previous version of xterm in the current environment, does it still behave properly? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Sat, 29 Aug 2009, Gavin McCullagh wrote: > I downgraded and it made no difference, the xterms are still white: A packager may have made changes to the X resources which would show up in the output from "xrdb -query". -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 421261] Re: xterm background colour used to be black, now white
On Sat, 29 Aug 2009, Gavin McCullagh wrote: > gavi...@teenie:~$ xrdb -query > Xcursor.size: 18 > Xcursor.theme: Human > Xcursor.theme_core: true > Xft.antialias: 1 > Xft.dpi:96 > Xft.hinting:1 > Xft.hintstyle: hintslight > Xft.lcdfilter: lcddefault > Xft.rgba: rgb > > Not sure I see anything there nor I - no foreground or background strings there. But that's one of the places I'd look, since #241 comes up with the wrong color. The other would be the output of appres XTerm appres UXTerm which would list _most_ of the resource settings seen by xterm and uxterm respectively. (If it doesn't show up there, it's harder to isolate - that's when I give up on the packaged binary and compile xterm with debugging traces, so I can see what resources it has ;-). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
