Collin Monahan wrote:
I noticed Lynx kept changing my window title. According to the source code it
was a call to SetConsoleTitle, part of the Windows API. ...
Then I created a version of the program to compile under GCC. ...
These may not be appropriate to use with an xterm window.
I noticed Lynx kept changing my window title. According to the source code it
was a call to SetConsoleTitle, part of the Windows API. Rather than modifying
the Lynx source code I wrote a short console program in Visual C++ which I can
use after exiting Lynx. It compiled under Visual Studio 2010
On 01/07/2010 04:37 PM, Collin Monahan wrote:
I noticed Lynx kept changing my window title. According to the source
code it was a call to SetConsoleTitle, part of the Windows API. Rather
than modifying the Lynx source code I wrote a short console program in
Visual C++ which I can use after
On 01/07/2010 04:38 PM, Larry Hall (Cygwin) wrote:
Does title in the CYGWIN environment variable no longer work?
I'm not familiar with that setting. I tried
export title=1
export title
export TITLE=1
export TITLE
Following each of those commands I tried running other ones (ls, grep), and the
Using the console window, I keep the Cygwin window title the same as much as
I can. It works pretty well (for the commands I happen to use) by setting
notitle in the CYGWIN variable and putting these lines in .bashrc:
settitle() { printf %s $'\033']2;$@$'\007\033']1;$@$'\007'; }
export
On 2010-01-07 21:52Z, Collin Monahan wrote:
On 01/07/2010 04:38 PM, Larry Hall (Cygwin) wrote:
Does title in the CYGWIN environment variable no longer work?
It still works in 1.7.1 .
I'm not familiar with that setting. I tried
export title=1
If you do:
export CYGWIN=$CYGWIN title ;
6 matches
Mail list logo
