Ashok Vadekar wrote:
Apologies for violating sane quoting convention, but I'm working off a crapberry.
Wrt to window titles: change your PS1 prompt to no longer reassign the title with the pwd (assuming you still have the default definition from /etc/profile (or similar)) and use the same escape
ginal Message -
From: cygwin-ow...@cygwin.com
To: cygwin@cygwin.com
Sent: Thu Jan 15 23:21:31 2009
Subject: Re: First Pass at mintty documentation; etc.
Andy Koppe wrote:
> Lee D. Rothstein wrote:
>
>> > "\e[1;5A": history-search-backward
>> > "\e[1;5B&qu
Lee D. Rothstein wrote:
> Andy Koppe wrote:
>> --
>> Chuck
>>
> Nice example! Who is "Chuck"?
Me. As I explained to Andy off-list, the 'Virtual Identify' Thunderbird
plugin got kinda confused, and tried to pass off my email as if Andy had
sent it. Bad Virtual Identity! No Cookie!
--
Chuck
-
Andy Koppe wrote:
Andy Koppe wrote:
Lee D. Rothstein wrote:
I do lots of bash scripting including Windows/DOS commands, and I
can think of only one character cell app that ever gave me any
trouble from rxvt or xterm (whatever that app is -- I think a
Kit app), I found a work-around and
Andy Koppe wrote:
Lee D. Rothstein wrote:
> "\e[1;5A": history-search-backward
> "\e[1;5B": history-search-forward
Perhaps I don't understand this 'bash' feature, but it doesn't
seem to work for me.
Start typing a command, press Ctrl-Up, and it finds the previous line
in the history that
On Thu, Jan 15, 2009 at 12:24 AM, Andy Koppe wrote:
> Speaking of history, does anyone know why xterm and rxvt diverged so much on
> modifier keycodes and why the xterm codes ended up being six characters
> long?
Because rxvt failed to adhere to the relevant standards[1].
[1] http://www.ecma-inte
On Thu, Jan 15, 2009 at 1:02 AM, Andrew DeFaria wrote:
> In my 25 years of working on such systems I can probably count on 2 fingers
> the number of times such a situation has arose and what I did was Control-C
> then Control-R again.
Sure. I'm not disagreeing; I was more looking for a plausible
Mark J. Reed wrote:
True, but that's only one direction of history search, albeit the most
commonly useful one. For those cases where you're somewhere back in
your history and need to search forward, what do you do?
In my 25 years of working on such systems I can probably count on 2
fingers th
On Thu, Jan 15, 2009 at 05:44:09AM +, Andy Koppe wrote:
>Chuck Wilson wrote:
>>"full screen" or "DOS" is a red herring. Any program that does
>>something like the following, if compiled as a native program, won't
>>work in rxvt (or MinTTY, or cygwin/cmd-shell-with-CYGWIN=tty):
>>
>> #include
Chuck Wilson wrote:
"full screen" or "DOS" is a red herring. Any program that does something
like the following, if compiled as a native program, won't work in rxvt
(or MinTTY, or cygwin/cmd-shell-with-CYGWIN=tty):
#include
main() {
int c;
while ((c = getc(stdin)) != EOF) fputc(c, stdout);
Andrew DeFaria wrote:
> "\e[1;5A": history-search-backward
> "\e[1;5B": history-search-forward
Perhaps I don't understand this 'bash' feature, but it doesn't seem
to work for me.
Start typing a command, press Ctrl-Up, and it finds the previous line
in the history that started like that.
Why
On Wed, Jan 14, 2009 at 10:18 PM, Andrew DeFaria wrote:
> Why not simply type Ctrl-R then the first few letters of a command (or some
> letters in the middle of a command). Works great! Requires no support from
> any terminal emulator...
True, but that's only one direction of history search, albei
Andy Koppe wrote:
Lee D. Rothstein wrote:
> "\e[1;5A": history-search-backward
> "\e[1;5B": history-search-forward
Perhaps I don't understand this 'bash' feature, but it doesn't seem
to work for me.
Start typing a command, press Ctrl-Up, and it finds the previous line
in the history that s
Andy Koppe wrote:
> Lee D. Rothstein wrote:
>> I do lots of bash scripting including Windows/DOS commands, and I
>> can think of only one character cell app that ever gave me any
>> trouble from rxvt or xterm (whatever that app is -- I think a
>> Resource Kit app), I found a work-around and never n
Lee D. Rothstein wrote:
> "\e[1;5A": history-search-backward
> "\e[1;5B": history-search-forward
Perhaps I don't understand this 'bash' feature, but it doesn't
seem to work for me.
Start typing a command, press Ctrl-Up, and it finds the previous line in
the history that started like that.
Andy Koppe wrote:
> Lee D.Rothstein wrote:
>> Hi, I've taken a first pass at distilling my experience with
>> 'mintty' and the [ahem] discussion, here, about it into a text
>> file (see attachment mintty.{h})
> Thanks, that's a nice surprise!
Okay, since you at least didn't hate it, I'll plug
On Sun, Jan 11, 2009 at 10:18:32PM +, Andy Koppe wrote:
>> @@ What "alternate screen"? @@
>
> Good question. It's vt100 lingo for a second logical screen that
> wholescreen apps such as editors normally use, often through the (n)curses
> library. (I'm taking "wholescreen" to mean an app contr
On 1/11/09, Andy Koppe wrote:
> Lee D.Rothstein wrote:
> >= Is there an alternate screen toggle in 'mintty' as there is
> > in 'xterm'?
> >
>
> I didn't know xterm actually had a UI for this. Do people find this useful?
If we're talking about switching between the regular screen and the
Lee D.Rothstein wrote:
Hi, I've taken a first pass at distilling my experience with
'mintty' and the [ahem] discussion, here, about it into a text
file (see attachment mintty.{h})
Thanks, that's a nice surprise!
Speed
It's quite funny, I didn't realise that until people here pointed it
o
19 matches
Mail list logo
