On Tue, 4 Oct 2016 10:13:47 -0400 Ross Vandegrift said:
> Hi all,
>
> On one system, terminology is interpreting presses of "<" as if I
> pressed ">". Comma is unaffected. No other application does this.
> Remote terminology doesn't do it, so I think it must be in the local
On 16-10-04 10:38, Ross Vandegrift wrote:
> On Tue, Oct 04, 2016 at 03:28:24PM +0100, Tom Hacohen wrote:
> > Is "<" rendered as "<", or as ">"? Could you maybe try a different shell
> > (I'm just making random suggestions at this point)?
>
> Keypresses of < are rendered ">". Apps interpret it
On Tue, Oct 04, 2016 at 03:28:24PM +0100, Tom Hacohen wrote:
> Is "<" rendered as "<", or as ">"? Could you maybe try a different shell
> (I'm just making random suggestions at this point)?
Keypresses of < are rendered ">". Apps interpret it as > (shell
redirection and less navigation are very
On 04/10/16 15:23, Ross Vandegrift wrote:
> On Tue, Oct 04, 2016 at 03:16:34PM +0100, Tom Hacohen wrote:
>>> On one system, terminology is interpreting presses of "<" as if I
>>> pressed ">". Comma is unaffected. No other application does this.
>>> Remote terminology doesn't do it, so I think
On Tue, Oct 04, 2016 at 03:16:34PM +0100, Tom Hacohen wrote:
> > On one system, terminology is interpreting presses of "<" as if I
> > pressed ">". Comma is unaffected. No other application does this.
> > Remote terminology doesn't do it, so I think it must be in the local
> > config.
> >
> >
On 04/10/16 15:13, Ross Vandegrift wrote:
> Hi all,
>
> On one system, terminology is interpreting presses of "<" as if I
> pressed ">". Comma is unaffected. No other application does this.
> Remote terminology doesn't do it, so I think it must be in the local
> config.
>
> Any ideas on how I
Hi all,
On one system, terminology is interpreting presses of "<" as if I
pressed ">". Comma is unaffected. No other application does this.
Remote terminology doesn't do it, so I think it must be in the local
config.
Any ideas on how I can track this down?
Ross