mlterm-dev-en Mailing List for mlterm(Multi Lingual TERMinal emulator)

 Hi,

 This is to announce the release of mlterm version 3.9.3

 https://github.com/arakiken/mlterm/archive/refs/tags/3.9.3.tar.gz
 https://github.com/arakiken/mlterm/releases/tag/3.9.3

 SHA1 (mlterm-3.9.3.tar.gz) = 2c60714141ab98b58fad41b11e12d2d0e1a598be

Overview of changes from 3.9.2
===============================
ver 3.9.3
* mlterm-wl supports xdg-decoration.
* Add --disable-compact-truecolor option to ./configure script.
* Add vte 0.68 API symbols to libvte compatible library.
* Add libvterm 0.2 API symbols to libvterm compatible library.
* Add --sdpr / simple_scrollbar_dpr option.
  (https://github.com/arakiken/mlterm/issues/64)
* Set "COLORTERM=truecolor" environmental variable.
  (https://github.com/arakiken/mlterm/issues/36)
* Update unicode property table (generated from UnicodeData.txt and
  EastAsianWidth.txt) to version 15.0.0.
* Support mosh-1.4.0.
* Merge patches:
  https://github.com/arakiken/mlterm/pull/45.
  https://github.com/arakiken/mlterm/pull/46.
  https://github.com/arakiken/mlterm/pull/48.
  https://github.com/arakiken/mlterm/pull/49.
  https://github.com/arakiken/mlterm/pull/55. (Add --role / wm_role option)
  https://github.com/arakiken/mlterm/pull/57.
  https://github.com/arakiken/mlterm/pull/61.
  https://github.com/arakiken/mlterm/pull/62.
  https://github.com/arakiken/mlterm/pull/63.
* Bug fixes:
  Fix https://github.com/arakiken/mlterm/issues/34.
  Fix https://github.com/arakiken/mlterm/issues/35.
  Fix https://github.com/arakiken/mlterm/issues/39.
  Fix https://github.com/arakiken/mlterm/issues/44.
  Fix https://github.com/arakiken/mlterm/issues/50.
  Fix https://github.com/arakiken/mlterm/issues/51.
  Fix https://github.com/arakiken/mlterm/issues/53.
  Fix https://twitter.com/isaki68k/status/1555895011991883783.
  Fix segfault in starting mlterm with --dyncomb and --otl.
---
Araki Ken
ara...@us...

On Sun, Sep 25 2022, Yuri D'Elia wrote:
> U+1F300-1FADF=Noto Emoji
>
> sadly it crashes on some glyphs (for example U+1f3b6 🎶) with the
> following:
>
> X Error of failed request:  BadLength (poly request too large or internal Xlib length error)
>   Major opcode of failed request:  139 (RENDER)
>   Minor opcode of failed request:  20 (RenderAddGlyphs)
>   Serial number of failed request:  464
>   Current serial number in output stream:  484
>
> Aside from the crash, I'm not a fan of color fonts. I wonder if there
> would be a way to force rendering to be grayscale and match my requested
> foreground color as well.

To answer myself, I have some extra info to provide. Since my system has
both "Noto Emoji" and "Noto Color Emoji", the color variant was
preferred via fontconfig on debian.

It turns out we can force a color-selection using an fc attribute:

U+1F300-1FADF=Noto Emoji:color=false

and this correctly selects the b&w version. However this applies a
filter on the font attributes so it doesn't seem to be possible to
_force_ grayscale rendering on a font that has colored glyphs.

I'm increasingly finding emojis in git commit messages (!) and I was
trying to get something to show instead of an anonymous square block.

I tried to install the mostly black&white "Noto Emoji" font:

https://fonts.google.com/noto/specimen/Noto+Emoji

and map the emoji block with it ~/.mlterm/aafont:

U+1F300-1FADF=Noto Emoji

sadly it crashes on some glyphs (for example U+1f3b6 🎶) with the
following:

X Error of failed request:  BadLength (poly request too large or internal Xlib length error)
  Major opcode of failed request:  139 (RENDER)
  Minor opcode of failed request:  20 (RenderAddGlyphs)
  Serial number of failed request:  464
  Current serial number in output stream:  484

Aside from the crash, I'm not a fan of color fonts. I wonder if there
would be a way to force rendering to be grayscale and match my requested
foreground color as well.

On NetBSD 9.2, mlterm 3.9.2 I am getting these errors:

    Jul 19 14:35:59[5802] Failed to open pty
    Jul 19 14:35:59[5802] Unable to open screen.

Any specific things I should check for?

-- 
Mayuresh

 Hi,

 This is to announce the release of mlterm version 3.9.2

 https://github.com/arakiken/mlterm/archive/refs/tags/3.9.2.tar.gz
 https://github.com/arakiken/mlterm/releases/tag/3.9.2

 SHA1 (mlterm-3.9.2.tar.gz) = 8117e73e51a6acfba4fab8cbdad188026d2d8471

Overview of changes from 3.9.1
===============================
ver 3.9.2
* Support Fcitx5.
* Support GTK4 for mlconfig. (./configure --with-gtk=4.0)
* Support CSI > Ps q (XTVERSION). (Response: DCS>|mlterm(3.9.2)ST)
* Add "MOSH_UDP_PORT" environmental variable to specify UDP port or port-range
  to communicate with a mosh server.
* Add INSERT_CLIPBOARD shortcut key.
  (https://github.com/arakiken/mlterm/issues/19)
* Add --fk / format_other_keys option (equivalent to "formatOtherKeys" of xterm), and
  change the default format of the escape sequence with modifyOtherKeys from
  CSI Ps; Ps u to CSI 27; Ps; Ps ~.
* Add --with-iconv, --disable-daemon, --disable-split and --disable-zmodem
  options to ./configure script.
* Add vte 0.66 API symbols to libvte compatible library.
* Show server list dialog at startup on Android.
* It is deprecated to use "mlterm" as the value of termtype / -y option.
* 'termcap' config file stops to accept multiple terminal types concated by '|'
  (e.g. xterm|xterm-256) as key.
* Arabic ligatures (U+644-U+622, U+644-U+622, U+644-U+625, U+644-U+627) occupy
  two logical columns instead of one even if --dyncomb option isn't specified.
* KBD_INPUT_NUM and MOUSE_INPUT_NUM environmental variables (for mlterm-fb)
  accept multiple device numbers by "<num>,<num>".
* Show "Config: key=value" only if shortcut keys whose format is
  "proto:(echo)key=value" is pressed.
* Merge patches:
  https://github.com/arakiken/mlterm/pull/5.
  https://github.com/arakiken/mlterm/pull/9.
  https://github.com/arakiken/mlterm/pull/12.
  https://github.com/arakiken/mlterm/pull/22.
* Bug fixes:
  Fix https://github.com/arakiken/mlterm/issues/15.
  Fix https://github.com/arakiken/mlterm/issues/18.
  Fix https://github.com/arakiken/mlterm/issues/24.
  Fix https://github.com/arakiken/mlterm/issues/28.
  Fix failure of restarting mlterm on Android. (Enbugged at 3.9.1)
  Fix segfault if mlterm screen with -t option goes outside of the display.
  Fix emoji glyphs becoming too large with cairo.
  Fix corrupt value of "word_separator" option which mlconfig outputs.
  Fix incompatibility with xterm in pressing Shift + a-z keys etc if modifyOtherKeys is 1.
  (https://github.com/arakiken/mlterm/issues/21)
  Fix segfault in opening a new roxterm tab with libvte compatible library on wayland.
---
Araki Ken
ara...@us...

On Sat, 2021-02-06 at 10:21 +0900, Araki Ken wrote:
>  Hi,
> 
> Vladimir Elisseev <vo...@vo...> wrote:
> > I just discovered that pseudo transparent background
> > (use_transbg=true)
> > works fine if depth=32 is set. It would be nice to add some notes
> > in
> > the man pages about that.
> > 
> > On Thu, 2021-02-04 at 17:16 +0100, Vladimir Elisseev wrote:
> > > I tried awesome wm recently and mlterm crashes while dragging the
> > > mlterm window and the window crosses left or bottom edge of the
> > > screen.
> > > This crash occurs only when pseudo transparent background is
> > > enabled.
> > > I'm using mlterm for a long while and can't really remember any
> > > crashes, but this one is quite interesting, that's why initially
> > > I
> > > reported a bug at
> > > https://github.com/awesomeWM/awesome/issues/3256.
> > > I'd appreciate any thoughts regarding the described crash.
> 
>  I fixed this problem which happens if depth < 32.
> 
>  https://github.com/arakiken/mlterm/commit/122b22201e74b6bdf88b46a8620dd3cdc2c88985#diff-41b6a72cdaa3f65eb153fbc2132ee572d670702c72f3f17f392c1029dbfcaf0e
> 
>  Thanks for your report.
> 
>  Regards,
> 
> ---
> Araki Ken
> ara...@us...

Thank you for, as usual, quick replay and the fix!

Regards,
Vlad.

 Hi,

Vladimir Elisseev <vo...@vo...> wrote:
> I just discovered that pseudo transparent background (use_transbg=true)
> works fine if depth=32 is set. It would be nice to add some notes in
> the man pages about that.
> 
> On Thu, 2021-02-04 at 17:16 +0100, Vladimir Elisseev wrote:
>> I tried awesome wm recently and mlterm crashes while dragging the
>> mlterm window and the window crosses left or bottom edge of the
>> screen.
>> This crash occurs only when pseudo transparent background is enabled.
>> I'm using mlterm for a long while and can't really remember any
>> crashes, but this one is quite interesting, that's why initially I
>> reported a bug at https://github.com/awesomeWM/awesome/issues/3256.
>> I'd appreciate any thoughts regarding the described crash.

 I fixed this problem which happens if depth < 32.

 https://github.com/arakiken/mlterm/commit/122b22201e74b6bdf88b46a8620dd3cdc2c88985#diff-41b6a72cdaa3f65eb153fbc2132ee572d670702c72f3f17f392c1029dbfcaf0e

 Thanks for your report.

 Regards,

---
Araki Ken
ara...@us...

Hello,

I just discovered that pseudo transparent background (use_transbg=true)
works fine if depth=32 is set. It would be nice to add some notes in
the man pages about that.

Regards,
Vlad.

On Thu, 2021-02-04 at 17:16 +0100, Vladimir Elisseev wrote:
> Hello,
> 
> I tried awesome wm recently and mlterm crashes while dragging the
> mlterm window and the window crosses left or bottom edge of the
> screen.
> This crash occurs only when pseudo transparent background is enabled.
> I'm using mlterm for a long while and can't really remember any
> crashes, but this one is quite interesting, that's why initially I
> reported a bug at https://github.com/awesomeWM/awesome/issues/3256.
> I'd appreciate any thoughts regarding the described crash.
> 
> Thank you in advance,
> Vlad.
> 
> 
> 
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlt...@li...
> https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en

Hello,

I tried awesome wm recently and mlterm crashes while dragging the
mlterm window and the window crosses left or bottom edge of the screen.
This crash occurs only when pseudo transparent background is enabled.
I'm using mlterm for a long while and can't really remember any
crashes, but this one is quite interesting, that's why initially I
reported a bug at https://github.com/awesomeWM/awesome/issues/3256.
I'd appreciate any thoughts regarding the described crash.

Thank you in advance,
Vlad.

"Yuri D'Elia" <wa...@th...> wrote:
> Do I understand correctly that mlterm acts differently just by setting
> termtype?

 Yes.
 mlterm acts like rxvt if termtype is rxvt, and act like xterm if termtype is xterm.
 The difference is defined in 'termcap' file.

> Given "mlterm" is still the default, what would be the recommended
> definition to avoid any sort of autodetection? mlterm3?

 The problem is that 'termcap' file included by debian is different from
the one I provide.
 This means that 'mlterm -y mlterm' hebaves differently (e.g. BCE)
in different environments.

 So, I'm sorry for the confusing situation, but it is not recommended to
use "mlterm" as the value of termtype option.

 "xterm" which the default value of termtype option is the least
problematic setting.
 I think mlterm works quite compatible with xterm now.

 If you use termtype=mlterm on debian with the new ncurses-term,
please remove ~/.mlterm/termcap and use the default setting of debian.

 Regards,
---
Araki Ken
ara...@us...

On Sun, Nov 29 2020, Araki Ken wrote:
>  This means that BCE is not supported if TERM=mlterm (or mlterm-256color).

Do I understand correctly that mlterm acts differently just by setting
termtype?

Given "mlterm" is still the default, what would be the recommended
definition to avoid any sort of autodetection? mlterm3?

 Hi,

"Yuri D'Elia" <wa...@th...> wrote:
> Hi everyone! I recently discovered an issue with an update of the
> ncurses-term definitions in debian.
> 
> If a custom termcap file ~/.mlterm/termcap is used to override some
> setting, the built-in "ut"/background-erase capability seems to be lost.
> 
> More details at:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975322#20

 Thanks.

 https://github.com/arakiken/mlterm/blob/master/etc/termcap contains 'mlterm' entry as follows.

mlterm:\
        k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~

 This means that BCE is not supported if TERM=mlterm (or mlterm-256color).

 But I've noticed that https://sources.debian.org/src/mlterm/3.9.0-1/debian/config-termcap/
which is installed on Debian GNU Linux doesn't have 'mlterm' entry for years.

 So mlterm supports BCE if not only TERM=xterm but TERM=mlterm on debian.

 I think ncurses-term definition was changed according to the behavior
of TERM=mlterm on debian.

 The behavior of TERM=mlterm seems complicated and mlterm becomes somewhat
more compatible with xterm now, so I'll write in the manual that it is
deprecated to use "mlterm" as the value of termtype option
in the next versoin (3.9.2).
---
Araki Ken
ara...@us...

Hi everyone! I recently discovered an issue with an update of the
ncurses-term definitions in debian.

If a custom termcap file ~/.mlterm/termcap is used to override some
setting, the built-in "ut"/background-erase capability seems to be lost.

More details at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975322#20

 Hi,

 This is to announce the release of mlterm version 3.9.1

 http://sourceforge.net/projects/mlterm/files/01release/mlterm-3.9.1/mlterm-3.9.1.tar.gz/download

 SHA1 (mlterm-3.9.1.tar.gz) = f05490c56528db2e2a88ca1979ebdf145c79a03f

Overview of changes from 3.9.0
===============================
ver 3.9.1
* Support copy mode which starts by Control+Shift+Return.
* Support OSC 1337;Setmark ST.
* Support CSI 3 J (ED) which clears backlog.
* Support gradle to build mlterm for Android. (See doc/en/README.android)
* Add --enable-utmp-suid option to ./configure script.
  (The default value is disabled.)
* Add --with-utmp option which specifies the way of accessing to utmp database
  to ./configure script.
* Add SCROLL_UP_TO_MARK, SCROLL_DOWN_TO_MARK and SET_MARK shortcut keys.
* Add resize_mode / --rz option, and drop scroll_on_resize / --sr option.
  (If you want to revert to the old behavior, specify --rz=none option.)
* Add emoji_file_format / --emojifmt option.
* Add libvterm 0.1 API symbols to libvterm compatible library.
* Add vte 0.62 API symbols to libvte compatible library.
* Drop SCROLL_DOWN and PAGE_DOWN shortcut keys.
* Drop use_extended_scroll_shortcut option and SCROLL_UP shortcut key is enabled
  by default. (If you want to disable it, add UNUSED=SCROLL_UP to ~/.mlterm/key.)
* Update unicode property table (generated from UnicodeData.txt and
  EastAsianWidth.txt) to version 13.0.0.
* letter_space / --csp option accepts negative value.
* libvte compatible library supports XInput2.
* Bug fixes:
  Fix a bug which caused a 'mlimgloader' process not to exit after loading a wall picture.
  (Enbugged at 3.8.8)
  Fix a bug which disabled keyboard and mouse on Haiku R1/beta2.
  Mlconfig starts correctly by Ctrl + RightClick on cygwin 3.1.4.
  Fix https://sourceforge.net/p/mlterm/mailman/message/37033060/
  Fix segfault of mlcc in exiting after changing configurations.
  Fix segfault in double click at RTL characters. (Enbugged at 3.6.2)
  Fix corruption of data transferred by "OSC 5379; scp ... ST".
  Fix https://github.com/arakiken/mlterm/issues/4.
  Fix	http://twitter.com/oshimyja/status/1320251099211649024.
---
Araki Ken
ara...@us...

 Hi,

> 1.  Shift+Control+v="proto:paste"
> 
> 2.  Shift+Control+Plus="proto:fontsize=larger"
>     Shift+Control++="proto:fontsize=larger"
> 
> 3.  Shift+Control+Minus="proto:fontsize=smaller"
>     Shift+Control+-="proto:fontsize=smaller"
> 
> Definitely I'm a novice using mlterm and can't find out how to specify these
> correctly.
> 
> For (1) I'm getting the traditional "^V" when I type that. A workaround is to
> specify: Shift+Insert="proto:paste" but I would like to have both.
>
> For (2) and (3) they only work if I totally change their shortcut (I have tried
> several names for "Plus", etc).

 How about configuring as follows ?

1 Shift+Control+V="proto:paste"
  (mlterm 3.9.1 will support Shift+Control+v)

2 Shift+Control+plus="proto:fontsize=larger"

3 Shift+Control+underscore="proto:fontsize=smaller"
  (If you use US keyboard, mlterm recognizes Shift+minus as underscore.
   I think it is confusing, so I'll look at ways to improve it.)

 Regards,
---
Araki Ken
ara...@us...

 Hi, I'm sorry for my late reply.

 Thanks for trying mlterm-wl and reporting problems.

Christian Victor Schulz <cv....@ma...> wrote:
> I would like to use mlterm-wl under sway, but I encounter a strange
> problem with my German keyboard layout. On the command line (bash), I
> can use umlauts (ö, ä, ü) as usual, but when I try to enter an umlaut in
> vim insert mode, strange things happen. It seems like mlterm-wl sends
> some character sequence to vim that starts with the umlaut but then
> causes vim to leave insert mode (Esc) and then repeat the previous
> action -- or something like that, I'm not sure. This does not happen
> with mlterm/X11.

 I fixed this problem.

> Another minor issue, probably fontconfig related as it also happens on
> Wayland only, is the exact placement of line drawing characters. Using
> the Inconsolata font, everything works fine on X11, but under Wayland,
> the line drawing characters do not line up properly.

 I struggled to fix this problem for weeks, and finally done.

 http://mlterm.sf.net/mlterm-wl-boxdraw.png

 https://github.com/arakiken/mlterm/archive/master.zip

 I significantly rewrote font subsystem for mlterm-wl, mlterm-fb,
mlterm-sdl2 and mlterm on Android.
 So if you find something strange, it would appreciate your report.

 Regards,
---
Araki Ken
ara...@us...

Hello,

First and foremost thanks for writing this program.

I'm trying to customize mlterm to match some of my previous experiences with
terminals. I would like to setup 3 shortcuts at ~/.mlterm/key:

1.  Shift+Control+v="proto:paste"

2.  Shift+Control+Plus="proto:fontsize=larger"
    Shift+Control++="proto:fontsize=larger"

3.  Shift+Control+Minus="proto:fontsize=smaller"
    Shift+Control+-="proto:fontsize=smaller"

Definitely I'm a novice using mlterm and can't find out how to specify these
correctly.

For (1) I'm getting the traditional "^V" when I type that. A workaround is to
specify: Shift+Insert="proto:paste" but I would like to have both.

For (2) and (3) they only work if I totally change their shortcut (I have tried
several names for "Plus", etc).

Can you help me with that?

Best,

--
Felipe Martins Vieira
I have transitioned to a new pgp key. Check my statement at:
https://goo.gl/GbfVv1
New Key Fingerprint: B145 230D 09E5 330C 9A0E  D5BC 1FEB 8CD8 FBFD C1CB
Mobile +55 11 971 066 250

On Wed, 10 Jun 2020, Christian Victor Schulz wrote:

> …
> 2. mlterm can masquerade as a libvte terminal. libvte is the library
> that is used by Gnome Terminal and many other terminal emulators
> (termite, guake, ...). The way this works is that the libvte library
> headers are replaced so that if you start e.g. a Gnome terminal, the
> terminal will actually be an mlterm within the normal Gnome terminal
> window. This could maybe solve your problem, but setting it up is a bit
> involved and I never tried it.  You can find instructions on how to do
> this in src/tip/gtk/README.
>
> Christian Schulz
> …

This is now working for me. Thanks for your help.

John

--
John Smith
jd...@ca...
https://bombay.indology.info

On Wed, 10 Jun 2020, Christian Victor Schulz wrote:

> On Wed, Jun 10, 2020 at 02:03:06PM +0200, John Smith wrote:
>> On Tue, 9 Jun 2020, Christian Victor Schulz wrote:
>>
>>> @John Smith:
>>> Have you tried using the Wayland version mlterm-wl? This may solve your
>>> problem.
>>
>> It does! Many thanks for this inspired suggestion. However, building mlterm-wl
>> produces a bare window without the normal Ubuntu decorations. I have never
>> compiled anything for Wayland before, and have googled without success for a
>> solution. So I need a little more help.
>>
>> John Smith
>
> Oh well, I forgot about that. The problem is that Gnome's Wayland
> session does not provide server-side window decorations; instead, the
> clients, e.g. mlterm, have to render the decorations themselves. This is
> called client-side window decorations. There have been lots of
> acrimonious discussions about this "feature" which you can read up on if
> you are interested, but this will not change anytime soon (there are
> other wayland compositors like sway that do have server-side
> decorations) and mlterm does not provide any window decorations. I don't
> know whether Araki Ken plans to implement this at some point.
>
> I forgot about it because I don't use Gnome anymore. Unfortunately, it
> probably renders my idea useless. Let's see what Araki Ken has to say
> about this, but for now, here are some other ideas:
>
> 1. Does the mouse behave weirdly under Gnome's X11 session as well? You
> can choose the X11 session when logging in. I think it is called "GNOME
> Classic". This is a somewhat temporary solution, but X11 support will
> probably not be dropped anytime soon.
>
> 2. mlterm can masquerade as a libvte terminal. libvte is the library
> that is used by Gnome Terminal and many other terminal emulators
> (termite, guake, ...). The way this works is that the libvte library
> headers are replaced so that if you start e.g. a Gnome terminal, the
> terminal will actually be an mlterm within the normal Gnome terminal
> window. This could maybe solve your problem, but setting it up is a bit
> involved and I never tried it.  You can find instructions on how to do
> this in src/tip/gtk/README.
>
> Christian Schulz
>
>
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlt...@li...
> https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en

Thank you for this very helpful and informative response!

I would not want to use the “Classic”  desktop, but I did check it out. mlterm
is not usable there either.

The idea of running a gnome-terminal that is really an mlterm sounds much more
appealing, and I shall try it out sometime in the next days.

John Smith


--
John Smith
jd...@ca...
https://bombay.indology.info

On Wed, Jun 10, 2020 at 02:03:06PM +0200, John Smith wrote:
> On Tue, 9 Jun 2020, Christian Victor Schulz wrote:
> 
> > @John Smith:
> > Have you tried using the Wayland version mlterm-wl? This may solve your
> > problem.
> 
> It does! Many thanks for this inspired suggestion. However, building mlterm-wl
> produces a bare window without the normal Ubuntu decorations. I have never
> compiled anything for Wayland before, and have googled without success for a
> solution. So I need a little more help.
> 
> John Smith

Oh well, I forgot about that. The problem is that Gnome's Wayland
session does not provide server-side window decorations; instead, the
clients, e.g. mlterm, have to render the decorations themselves. This is
called client-side window decorations. There have been lots of
acrimonious discussions about this "feature" which you can read up on if
you are interested, but this will not change anytime soon (there are
other wayland compositors like sway that do have server-side
decorations) and mlterm does not provide any window decorations. I don't
know whether Araki Ken plans to implement this at some point.

I forgot about it because I don't use Gnome anymore. Unfortunately, it
probably renders my idea useless. Let's see what Araki Ken has to say
about this, but for now, here are some other ideas:

1. Does the mouse behave weirdly under Gnome's X11 session as well? You
can choose the X11 session when logging in. I think it is called "GNOME
Classic". This is a somewhat temporary solution, but X11 support will
probably not be dropped anytime soon.

2. mlterm can masquerade as a libvte terminal. libvte is the library
that is used by Gnome Terminal and many other terminal emulators
(termite, guake, ...). The way this works is that the libvte library
headers are replaced so that if you start e.g. a Gnome terminal, the
terminal will actually be an mlterm within the normal Gnome terminal
window. This could maybe solve your problem, but setting it up is a bit
involved and I never tried it.  You can find instructions on how to do
this in src/tip/gtk/README.

Christian Schulz

On Tue, 9 Jun 2020, Christian Victor Schulz wrote:

> @John Smith:
> Have you tried using the Wayland version mlterm-wl? This may solve your
> problem.

It does! Many thanks for this inspired suggestion. However, building mlterm-wl
produces a bare window without the normal Ubuntu decorations. I have never
compiled anything for Wayland before, and have googled without success for a
solution. So I need a little more help.

John Smith

--
John Smith
jd...@ca...
https://bombay.indology.info

Upon closer inspection, it seems like mlterm-wl is appending a NUL when
I try to enter an umlaut. Thus, if I type "ö", it sends "ö^@". Bash
ignores this, but vim does not.


On Tue, Jun 09, 2020 at 11:06:32AM +0200, Christian Victor Schulz wrote:
> Hi,
> 
> I would like to use mlterm-wl under sway, but I encounter a strange
> problem with my German keyboard layout. On the command line (bash), I
> can use umlauts (ö, ä, ü) as usual, but when I try to enter an umlaut in
> vim insert mode, strange things happen. It seems like mlterm-wl sends
> some character sequence to vim that starts with the umlaut but then
> causes vim to leave insert mode (Esc) and then repeat the previous
> action -- or something like that, I'm not sure. This does not happen
> with mlterm/X11.
> 
> Another minor issue, probably fontconfig related as it also happens on
> Wayland only, is the exact placement of line drawing characters. Using
> the Inconsolata font, everything works fine on X11, but under Wayland,
> the line drawing characters do not line up properly.
> 
> Christian Schulz
> 
> 
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlt...@li...
> https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en

@John Smith:
Have you tried using the Wayland version mlterm-wl? This may solve your
problem.

Hi,

I would like to use mlterm-wl under sway, but I encounter a strange
problem with my German keyboard layout. On the command line (bash), I
can use umlauts (ö, ä, ü) as usual, but when I try to enter an umlaut in
vim insert mode, strange things happen. It seems like mlterm-wl sends
some character sequence to vim that starts with the umlaut but then
causes vim to leave insert mode (Esc) and then repeat the previous
action -- or something like that, I'm not sure. This does not happen
with mlterm/X11.

Another minor issue, probably fontconfig related as it also happens on
Wayland only, is the exact placement of line drawing characters. Using
the Inconsolata font, everything works fine on X11, but under Wayland,
the line drawing characters do not line up properly.

Christian Schulz

I have now compiled a minimalistic mlterm 3.9.0, using the options listed in
the README file to minimise the binary, and adding only --prefix=/usr/local
and --with-gui=xlib. The mouse behaviour is the same as with Ubuntu's
distribution version: all I can do with it is to highlight text and scroll up
and down.

I am assuming this behaviour is not intended, in which case there is evidently
a bug somewhere. I'll be happy to supply more details of my setup if they
would be helpful.

If I am mistaken and this behaviour is intentional, please can some way be
provided to switch it off? I would very much like to use mlterm, but cannot do
so while the mouse behaves in this way.

John Smith

--
John Smith
jd...@ca...
https://bombay.indology.info


On Wed, 27 May 2020, John Smith wrote:

> Ubuntu 20.04, Gnome shell 3.36.2 running under X11, Ubuntu distribution
> version of mlterm — version 3.8.9, Features: otl ssh implugin
> imagelib(builtin) utmp.
>
> I have configured mlterm for use with normal Roman and also Devanagari
> (Hindi). Both appear to work well.
>
> Once mlterm is displaying some text, if I move the mouse it behaves as if I
> were simultaneously pressing the left button: text is highlighted and the
> window scrolls up/down. Nothing I do seems to change this behaviour. I have
> tried modifying the settings for clipboard and scroll under “Others” in
> mlterm’s menu, but these changes seem to have no effect, and anyway they 
> don’t
> “stick” — they always revert to the default (clipboard selection checked, the
> two scroll options unchecked).
>
> The only item in my msg.log file is
>
> May 27 08:55:16[277993] Font(id 10d1) width(10) is not matched with standard 
> width(8).
>
> repeated whenever I switch into the Devanagari font.
>
> I would be happy to try compiling the current version of mlterm, but would
> need specific guidance on what options to use for ./configure.
>
> Thanks for any help,
> John Smith
>
> --
> John Smith
> jd...@ca...
> https://bombay.indology.info