TSE: Linux: Terminal: xterm

[knud van eeden]

Hello,

As now 

1. most if not all keys (as defined in the tse.ui) are very probably going to be working on Linux 4.50.14 or higher 

in the xterm terminal

2. and also when implemented it was recommended to run TSE in the xterm terminal as there it should work.

3. So it might be probably an idea to recommend in the official TSE documentation (read.me, ...) that it is recommended 

to use preferably the xterm terminal to run TSE on Linux.

4. And that that is also the gold standard to work from, e.g. when troubleshooting.

5. So making thus xterm the terminal standard for TSE for Linux.

5. Note: Given that there are so many terminal implementations (like Gnome, Relay, Mate, ...) which have in general very severe limitations (e.g. 30 percent of the TSE tse.ui keys do not work in those terminal types) with regard to TSE behavior when running TSE in those terminals it would thus be better to reduce the possibilities to basically 1 terminal (=xterm) and always work from there.

with friendly greetings

Knud van Eeden

[knud van eeden]

Updated:

> 2. and also when the mouse keys should be implemented it was recommended to run TSE in the xterm terminal as there it should work.

--

---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/semware/2028600775.2342818.1760365871581%40mail.yahoo.com.

[Guy Rouillier]

xterm is a very minimal terminal implementation, which of course is why people use it to represent a "vanilla" environment.  But any who spends a non-trivial amount of time using a terminal will not use xterm, but will use an alternative that supplies commonly-used functionality.  So I would vote against xterm being a "representative" terminal program.  I'm not saying anyone should use what I use (Mate Terminal, since I use the Mate DE.)  But pick one that is popular with terminal users, which is decidedly *not* xterm.

--

---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/semware/2028600775.2342818.1760365871581%40mail.yahoo.com.

-- 

Guy Rouillier

[knud van eeden]

One has no choice if wanting to have the most active TSE keys currently.

If you run Mate 60 percent of the keys work in TSE.

If you run xterm then up to 100 percent of the TSE keys can work now.

Just run 'showkey' in TSE and type your TSE keys in Mate, not much will work (why? Because Mate or the window manager or the OS fetches those

TSE keys by design. The same goes for e.g. gnome.

Up to you thus regarding choice of which terminal, xterm should be the preferred choice when working with TSE.

Not sure what Mate can do more or better than xterm further, xterm seems pretty complete (also).

with frienly greetings

Knud van Eeden

To view this discussion visit https://groups.google.com/d/msgid/semware/498afcd42925f29b9fa36ace2d4dc3b5dc110f1e.camel%40gmail.com.

[knud van eeden]

It is thus certainly not so that Semware should not want to include also (recommended or usable) terminals like Mate, Gnome, ...

It is thus the fact that the pre-conditions regarding TSE keys in those non-xterm terminals are by given external design (outside

of the scope and reach of TSE / Semware) are thus severely bad regarding possibilities.

[Claus Futtrup]

Hi Guy

I installed xterm in Ubuntu (it isn't installed by default).

Then in my normal terminal, using .bashrc, I configured a script for executing TSE in a separate terminal window (= xterm)...

No need to use xterm in your normal (default) terminal window.

Cheers,

Claus

To view this discussion visit https://groups.google.com/d/msgid/semware/498afcd42925f29b9fa36ace2d4dc3b5dc110f1e.camel%40gmail.com.