On 12/15/06, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Aaron Humphrey wrote on Friday, December 15, 2006 5:34 PM:
> Oddly enough, it seems to. In fact, just adding the '-c' option to
> NROFF in man.conf, without having to remove '-Tlatin' or add the '2>
> /dev/null' (which I'm not sure would work
On 12/18/06, Matthew Woehlke wrote:
Personally, I have never heard of '\e[22' turning off bold. My guess
would be that the real solution here is to fix the TERMINFO database.
As seen at http://rtfm.etla.org/xterm/ctlseq.html , under the section
"Functions using CSI, ordered by the final charact
Buchbinder, Barry (NIH/NIAID) [E] wrote:
Aaron Humphrey wrote on Friday, December 15, 2006 5:34 PM:
Oddly enough, it seems to. In fact, just adding the '-c' option to
NROFF in man.conf, without having to remove '-Tlatin' or add the '2>
/dev/null' (which I'm not sure would work under tcsh anyway
Aaron Humphrey wrote on Friday, December 15, 2006 5:34 PM:
> On 12/15/06, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>> I'm wondering whether this might be related to this old problem.
>> http://sources.redhat.com/ml/cygwin/2006-11/msg00734.html
>> I was having man pages where bold was not turn off
On 12/15/06, Buchbinder, Barry (NIH/NIAID) [E] wrote:
I'm wondering whether this might be related to this old problem.
http://sources.redhat.com/ml/cygwin/2006-11/msg00734.html
I was having man pages where bold was not turn off properly. If I
remember correctly, this suggestion fixed it for me.
Aaron Humphrey wrote on Friday, December 15, 2006 1:38 PM:
> On 12/14/06, Matthew Woehlke wrote:
>> Aaron Humphrey wrote:
>>> It seems to vary. I see it with 'man vim' and 'man printf' after
>>> the first screen, for instance, but not with 'man man', unless I
>>> pick just the right line. Which
This looks like a problem with ANSI attributes in a shell window. The
problem doesn't happen when running under xterm. It looks like
[22m turns off bold in a Xterm, but not a regular shell. Maybe
the "cygwin" entry needs to be fixed in /etc/termcap.
--
Unsubscribe info: http://cygwin.com/
On 12/14/06, Matthew Woehlke wrote:
Aaron Humphrey wrote:
> It seems to vary. I see it with 'man vim' and 'man printf' after the
> first screen, for instance, but not with 'man man', unless I pick just
> the right line. Which makes it seem less likely that it's a problem
> with the man page for
Aaron Humphrey wrote:
On 12/14/06, Matthew Woehlke wrote:
Does this only happen with the bash manpage, or do you see it with other
manpages as well?
It seems to vary. I see it with 'man vim' and 'man printf' after the
first screen, for instance, but not with 'man man', unless I pick just
the
On 12/14/06, Matthew Woehlke wrote:
Ok, this is useful; it sounds like 'man bash' is in fact leaving the
bold attribute turned on incorrectly. Aaron, in your case your prompt
does not clear the attribute; I assume "printf '\033[0m'" fixes things?
It does indeed.
Does this only happen with the
Aaron Humphrey wrote:
I've seen this as well, my prompt(and everything I type)turning white
if I don't go through the "bash" man page all the way to the end. I
note that "stty sane" does nothing, nor does hitting enter; my prompt
stays white. (This is in tcsh, where my "prompt" variable is "[EM
I've seen this as well, my prompt(and everything I type)turning white
if I don't go through the "bash" man page all the way to the end. I
note that "stty sane" does nothing, nor does hitting enter; my prompt
stays white. (This is in tcsh, where my "prompt" variable is "[EMAIL PROTECTED]
%c02]$".
Hi All...
I have also seen it on all my machines. I have a vanilla Cygwin bash PS1.
Thanks,
...Karl
From: Eric Lilja Subject: Re: Weird cosmetic bug after viewing bash man
page
Date: Thu, 14 Dec 2006 19:59:44 +0100
Dave Korn skrev:
On 14 December 2006 18:48, Eric Lilja wrote:
Well, the
Dave Korn skrev:
On 14 December 2006 18:48, Eric Lilja wrote:
Well, the prompt that is displayed directly after "man bash" exits
exhibits the hightlighted colors (only seems to happen for that
particular man page). If I issue the command stty sane, or any other
command, or simply press enter t
On 14 December 2006 18:48, Eric Lilja wrote:
> Well, the prompt that is displayed directly after "man bash" exits
> exhibits the hightlighted colors (only seems to happen for that
> particular man page). If I issue the command stty sane, or any other
> command, or simply press enter the next prom
Dave Korn skrev:
On 14 December 2006 18:26, Eric Lilja wrote:
Dave Korn skrev:
On 14 December 2006 17:43, Eric Lilja wrote:
If I press enter the prompt is restored to its normal appearance. A
picture exhibiting this cosmetic glith can be viewed at
student.stunet.se/hivemind/weird_cosmetic_b
On 14 December 2006 18:26, Eric Lilja wrote:
> Dave Korn skrev:
>> On 14 December 2006 17:43, Eric Lilja wrote:
>>> If I press enter the prompt is restored to its normal appearance. A
>>> picture exhibiting this cosmetic glith can be viewed at
>>> student.stunet.se/hivemind/weird_cosmetic_bug.png
Dave Korn skrev:
On 14 December 2006 17:43, Eric Lilja wrote:
Hello!
By chance, I noticed that if I view bash's man page and then press 'q'
to exit man, the prompt is colored more brightly than it is by default.
If I press enter the prompt is restored to its normal appearance. A
picture exhibit
On 14 December 2006 17:43, Eric Lilja wrote:
> Hello!
> By chance, I noticed that if I view bash's man page and then press 'q'
> to exit man, the prompt is colored more brightly than it is by default.
> If I press enter the prompt is restored to its normal appearance. A
> picture exhibiting this c
19 matches
Mail list logo
