> There is, but it isn't too serious: with NumLock off, Enter and the
> operator keys on the numpad don't work in orpie when running in xterm
> or mintty. That's because it doesn't seek to support the "application
> keypad mode" keycodes. (But users will probably have NumLock on anyway
> if they're
> > Hey! I'm glad to know that someone else is using orpie. I like it, which
> > is
> > why I packaged it for Cygwin, but I thought I might be the only one.
>
> I wasn't aware of it, but it does look rather good, with a pleasingly
> high geek factor.
Once you go RPN, you'll never go back.
>
2009/6/26 Mark Harig:
>> From the 0.4.0 release announcement:
>>
>> - MinTTY now has its own identity, instead of pretending to be an old
>> xterm. The ^E answerback string is "mintty", the ^[[c primary device
>> attribute command reports a vt100, and the ^[[>c secondary DA command
>> reports termi
2009/6/25 Andrew Schulman:
>> After upgrading to mintty-0.4.1-1, the Enter, +, -, *, and / keys on my
>> number pad no longer with in orpie. Reverting to mintty-0.4.0-2 solves
>> the problem. Also, running "TERM=cygwin orpie" also solves the problem.
>> (TERM=xterm by default for me. I have no idea
2009/6/26 Matt Wozniski:
>
> > There's a bit in the TIPS section of the manual on how to set any
> > environment variable using the shell's -c option, e.g.:
> >
> > mintty sh -c "TERM=xterm-256color emacs"
>
> Hm. Maybe I'm missing something, but - isn't this a place where using
> /bin/env would m
On Thu, Jun 25, 2009 at 3:25 PM, Andy Koppe wrote:
> There's a bit in the TIPS section of the manual on how to set any
> environment variable using the shell's -c option, e.g.:
>
> mintty sh -c "TERM=xterm-256color emacs"
Hm. Maybe I'm missing something, but - isn't this a place where using
/bin/
Thu, 25 Jun 2009 20:25:09 +0100 Andy Kope wrote:
>
> There is no documented way in mintty to change the TERM environment before
> the shell is started.
There's a bit in the TIPS section of the manual on how to set any
environment variable using the shell's -c option, e.g.:
mintty sh -c "TERM=x
> After upgrading to mintty-0.4.1-1, the Enter, +, -, *, and / keys on my
> number pad no longer with in orpie. Reverting to mintty-0.4.0-2 solves
> the problem. Also, running "TERM=cygwin orpie" also solves the problem.
> (TERM=xterm by default for me. I have no idea where that comes from.)
>
2009/6/25 David Rothenberge:
>>> After upgrading to mintty-0.4.1-1, the Enter, +, -, *,
>>> and / keys on my number pad no longer with in orpie.
>>> Reverting to mintty-0.4.0-2 solves the problem.
>>
>> Sure about 0.4.0-2?
>
> Yup. I checked it a number of times.
Ah, you're right; I hadn't tried i
On 6/25/2009 12:17 PM, Andy Koppe wrote:
2009/6/25 David Rothenberger:
After upgrading to mintty-0.4.1-1, the Enter, +, -, *,
and / keys on my number pad no longer with in orpie.
Reverting to mintty-0.4.0-2 solves the problem.
Sure about 0.4.0-2?
Yup. I checked it a number of times.
--
Davi
2009/6/25 Mark Harig:
> > (TERM=xterm by default for me. I have no idea where that comes from.)
>
> This is documented in the manual page for 'mintty':
>
>> TERM variable
>> The TERM variable for the child process is set to "xterm", so that pro‐
>> grams that pay attention to it expect xterm keycod
2009/6/25 David Rothenberger:
> After upgrading to mintty-0.4.1-1, the Enter, +, -, *,
> and / keys on my number pad no longer with in orpie.
> Reverting to mintty-0.4.0-2 solves the problem.
Sure about 0.4.0-2? I'm finding the behaviour changed between 0.4-rc3
and 0.4-rc4. That's when the keycode
> (TERM=xterm by default for me. I have no idea where that comes from.)
This is documented in the manual page for 'mintty':
TERM variable
The TERM variable for the child process is set to "xterm", so that pro‐
grams that pay attention to it expect xterm keycodes and output xterm‐
compatible con
13 matches
Mail list logo
