Menu
▾
▴
mlterm-dev-en — mlterm mailing list(English)
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(44) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(44) |
Feb
(22) |
Mar
|
Apr
(3) |
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(7) |
Sep
(8) |
Oct
(14) |
Nov
(8) |
Dec
(32) |
| 2003 |
Jan
(17) |
Feb
(4) |
Mar
(7) |
Apr
(2) |
May
(5) |
Jun
(17) |
Jul
(18) |
Aug
(2) |
Sep
(2) |
Oct
(7) |
Nov
|
Dec
(4) |
| 2004 |
Jan
(4) |
Feb
(2) |
Mar
(7) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
|
Aug
(14) |
Sep
(10) |
Oct
(57) |
Nov
(23) |
Dec
(2) |
| 2005 |
Jan
(47) |
Feb
(9) |
Mar
(25) |
Apr
(1) |
May
|
Jun
(7) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(6) |
Nov
(1) |
Dec
(6) |
| 2006 |
Jan
(3) |
Feb
(3) |
Mar
(20) |
Apr
(12) |
May
(20) |
Jun
(17) |
Jul
(9) |
Aug
(7) |
Sep
(1) |
Oct
(10) |
Nov
(5) |
Dec
(7) |
| 2007 |
Jan
(9) |
Feb
(10) |
Mar
(24) |
Apr
(27) |
May
(4) |
Jun
(8) |
Jul
(16) |
Aug
(38) |
Sep
(10) |
Oct
(5) |
Nov
(6) |
Dec
(8) |
| 2008 |
Jan
(6) |
Feb
|
Mar
(2) |
Apr
(3) |
May
(3) |
Jun
(6) |
Jul
(6) |
Aug
(3) |
Sep
(10) |
Oct
(10) |
Nov
(42) |
Dec
(37) |
| 2009 |
Jan
(13) |
Feb
(10) |
Mar
(20) |
Apr
(22) |
May
(32) |
Jun
(15) |
Jul
(33) |
Aug
(9) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(12) |
| 2010 |
Jan
(9) |
Feb
(8) |
Mar
|
Apr
(6) |
May
(7) |
Jun
(12) |
Jul
(1) |
Aug
|
Sep
(3) |
Oct
(9) |
Nov
(3) |
Dec
(6) |
| 2011 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(4) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(2) |
Feb
|
Mar
(10) |
Apr
(12) |
May
(10) |
Jun
(9) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
(24) |
Dec
(6) |
| 2013 |
Jan
(2) |
Feb
(2) |
Mar
(6) |
Apr
(12) |
May
(24) |
Jun
(7) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(9) |
| 2014 |
Jan
(29) |
Feb
(7) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(5) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(1) |
| 2015 |
Jan
(1) |
Feb
(1) |
Mar
(2) |
Apr
|
May
(5) |
Jun
(5) |
Jul
(1) |
Aug
(5) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2016 |
Jan
(1) |
Feb
(2) |
Mar
(5) |
Apr
(6) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(5) |
| 2017 |
Jan
(1) |
Feb
(5) |
Mar
(2) |
Apr
(2) |
May
(18) |
Jun
(1) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
(2) |
Feb
|
Mar
(15) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
| 2019 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(12) |
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(1) |
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
(3) |
Apr
(1) |
May
(2) |
Jun
(7) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(1) |
| 2021 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Araki K. <ara...@us...> - 2018-03-11 05:16:03
|
Hi, > I noticed mlterm supports the iterm2's OSC1337 inline images, which I > actually prefer to sixel's due to a number of reasons. However, the > preserveAspectRatio attribute is not currently supported. > From the iterm docs: > preserveAspectRatio: If set to 0, then the image's inherent aspect ratio > will not be respected; otherwise, it will fill the specified width and > height as much as possible without stretching. Defaults to 1. > I modified ranger (http://ranger.nongnu.org/), which supports inline > previews via a number of methods to use OSC1337 on mlterm as opposed to > sixel. This doesn't require image recoding on the ranger side, which is > a big plus. The image is currently filled inside the ranger's preview > area, but preserveAspectRatio is needed to correctly display the image > in this case. > Would it be possible to implement also this attribute? Sorry for my late reply. Mails from mlterm-dev-en list didn't reached to me for months. Mlterm now supports OSC1337 'preserveAspectRatio' option on x11. Please check http://bitbucket.org/arakiken/mlterm/get/tip.tar.gz Regards, --- Araki Ken ara...@us... |
|
From: Araki K. <ara...@us...> - 2018-03-07 14:41:36
|
Hi, This is to announce the release of mlterm version 3.8.5 http://sourceforge.net/projects/mlterm/files/01release/mlterm-3.8.5/mlterm-3.8.5.tar.gz/download SHA1 (mlterm-3.8.5.tar.gz) = 336b75f05f4cd689410253ea8856d3d1f3f1b706 Overview of changes from 3.8.4 =============================== ver 3.8.5 * Support libvterm (https://launchpad.net/libvterm) compatible library partially. * Support DRCS-Sixel. (See drcssixel/DRCS-SIXEL-v2 and https://qiita.com/arakiken/items/626b02cd857d20c12fbc) * Support SDL2. (Build mlterm with --with-gui=sdl2 option.) (see doc/en/README.sdl2) * Support ligature of "Fira Code" font in -otl option. * Add --halfwidth / "unicode_half_width_areas" option. * Add --emoji / "emoji_path" option which makes mlterm to use a specified emoji font (NotoColorEmoji.ttf etc) instead of image files in ~/.mlterm/emoji. * Add vte 0.50.0 API symbols to libvte compatible library. * Treat not only U+1F1000-1F6FF but also U+1F900-1F9FF characters as emoji. * Drop "show_picture" and "add_frame" from OSC 5379. * Bug fixes: Fix corrupt screen in showing inline pictures if "use_ot_layout" option is true. --- Araki Ken ara...@us... |
|
From: Boyuan Y. <07...@gm...> - 2018-01-31 02:22:32
|
Dear mlterm developers, I am the current co-maintainer of fcitx in Debian. The latest version of fcitx (4.2.9.5, released on 2017-11-09) seems to have broken mlterm's fcitx support due to a library SONAME bump in libfcitx-gclient. Some functions you're using in mlterm is gone (moved away from header file). This bug has been submitted downstream in Debian: https://bugs.debian.org/887711 Please help investigate into this problem and fix it if possible. Regards, Boyuan Yang |
|
From: Yuri D'E. <wa...@th...> - 2018-01-20 14:15:01
|
Hi everyone, I noticed mlterm supports the iterm2's OSC1337 inline images, which I actually prefer to sixel's due to a number of reasons. However, the preserveAspectRatio attribute is not currently supported. >From the iterm docs: preserveAspectRatio: If set to 0, then the image's inherent aspect ratio will not be respected; otherwise, it will fill the specified width and height as much as possible without stretching. Defaults to 1. I modified ranger (http://ranger.nongnu.org/), which supports inline previews via a number of methods to use OSC1337 on mlterm as opposed to sixel. This doesn't require image recoding on the ranger side, which is a big plus. The image is currently filled inside the ranger's preview area, but preserveAspectRatio is needed to correctly display the image in this case. Would it be possible to implement also this attribute? |
|
From: Araki K. <ara...@us...> - 2017-12-02 17:34:32
|
Hi, This is to announce the release of mlterm version 3.8.4 http://sourceforge.net/projects/mlterm/files/01release/mlterm-3.8.4/mlterm-3.8.4.tar.gz/download SHA1 (mlterm-3.8.4.tar.gz) = ffc66275ed60b376675240763c4b802a2b8d8bed Overview of changes from 3.8.3 =============================== ver 3.8.4 * Support DECSLPP, DECSCPP, DECBBSM, DECRQTSR, DECCTR, DECRQPSR, DECSNLS, DECSTGLT, DECRSPS, DECSR, CSI 7 t, CSI 9;1 t, CSI ? Pm s, CSI ? Pm r, CSI 34 [hl], CSI 53 m and CSI 55 m. * Support DECSASD, DECSSDT unless vertical mode is enabled. * Support 90-degree rotation of alphabet glyphs in vertical mode (cjk alone) on framebuffer, wayland and android if freetype is enabled. * Support sticky shift key of skk im module, and change the format of skk option from "skk:[dictionary]" to "skk:dict=[dictionary],sskey=[sticky shift key]". * Add "use_vertical_cursor" and "click_interval" to OSC 5379, 5380 and 5381. * Add "ot_features" and "ot_script" to OSC 5380 and 5381. * Add "Features" and "Script" buttons to "Encoding" tab of mlconfig. * Add "Underline pos (pixels)" and "Baseline pos (pixel)" to "Font" tab of mlconfig. * Add "Double click interval (msec)", "Send keys to all windows" and "Trim trailing CR/LF in pasting" to "Others" tab of mlconfig. * Add doc/en/ControlSequences which lists escape/control sequences which mlterm supports. * Change the default value of "use_vertical_cursor" option from false to true. * Drop "CSI ? 9500 [hl]". * Improve processing sixel graphics on pseudo color framebuffer. * Merge patches: https://sf.net/p/mlterm/patches/_discuss/thread/f5dc445d/0fc3/attachment/fix_spelling.diff * Bug fixes: Fix impossibility of keyborad and pointer input after switching virtual consoles on wayland. Fix unexpectedly having privilege in opening a shell on startup of mlterm built with brlapi. Fix Pl, Pc and Pp of XCPR and CPR. Fix corruption of TBC (CSI g), CTC (CSI W) and DECATC(CSI ,}). --- Araki Ken ara...@us... |
|
From: Yuri D'E. <wa...@th...> - 2017-11-19 23:55:28
|
Hi everyone. I'm trying mlterm 3.8.3 from Debian. I'm using multiple monitors with a different resolution so I'd like to specify font sizes using points. use_point_size=true only works with type_engine=xft in my case. If I leave type_engine=cairo (the default), fontsize is always in pixels irregardless of the status of use_point_size. Both xrandr and the Xft.dpi xresource agree and are set to 140dpi in my case. Any reason cairo isn't picking it up? |
|
From: Steve W. <ste...@gm...> - 2017-10-01 19:45:22
|
Hi,
I've been looking into the effectiveness of various modern terminal
emulators for the use by speakers of Indic languages, such as Hindi,
Gugarati, Bengali, etc. Of course mlterm caught my eye. But I've not
got it working to my satisfaction.
I installed it on my Linux Mint system, but found that it wouldn't
display any Indic text at all. It turned out, the distro version is
built with 'use_ind' disabled. Well, that's unfortunate... no problem
-- I built it myself with 'use_ind' turned on, like so
./configure -with-tools=use_ind
This custom build of mlterm displays Indic letters, but the text is
practically unreadable, because Indic text shaping has not been
applied, and the letters are all jumbled up -- in Hindi, viramas are
always visible and not used to group consonants, so that an i-vowel
after a consonant cluster is not moved to the head of the cluster.
And so on. This kind of processing is usually handled by the font
rendering layer, but it appars that functionality has been disabled.
I'm talking about the Indic text transoformations described in the
Unicode Standard ch12, for instance in the section on Hindi, under the
heading "Principles of the Devanagari Script".
Your competitor, KDE's Konsole, does a pretty good job rendering
Devanagari script, on the same system, using the same font. (Even it
is challenged by line wrapping of Indic text though!)
Have I missed some configuration option?
Thanks!
|
|
From: Araki K. <ara...@us...> - 2017-09-22 20:01:21
|
Hi, This is to announce the release of mlterm version 3.8.3 http://sourceforge.net/projects/mlterm/files/01release/mlterm-3.8.3/mlterm-3.8.3.tar.gz/download SHA1 (mlterm-3.8.3.tar.gz) = 2b0a4fcb04474c63c64c48231a1c1bf50e7eb56b Overview of changes from 3.8.2 =============================== ver 3.8.3 * Add "trim_trailing_newline_in_pasting" / --trim option which removes trailing newline characters in pasting text. * Add "broadcast" / --bc option which broadcasts input or pasted characters to all ptys whose value of "ignore_broadcasted_chars" option is false. * Add "ignore_broadcasted_chars" / --ibc option. * Add "Next pty", "Previous pty" and "Close screen" to context menu on Android. * Add "next_pty", "prev_pty" and "close_screen" to OSC 5379. * Add "fontconfig" to OSC 5380. * Support libssh2 on MacOSX/Cocoa. * Support ModifyCursorKeys and ModifyFunctionKeys of xterm. * Support OSC 0 and OSC 1 on MacOSX/Cocoa. * Support _NET_WM_NAME and _NET_ICON_NAME properties on xlib. * Support "CSI > Ps t" and "CSI > Ps T". * Support "CSI 20 h" and "CSI 20 l" (LNM). * Support right click menu on libvte compatible library on wayland. * Support fcitx input method module on wayland. * Support italic on MacOSX/Cocoa. * Remove --hscr / "screen_height_ratio" option. * Change the default sequences of Modifier+Function and Modifier+Cursor keys from xterm's old/obsolete ones to modern ones. (e.g. Shift+F1 outputs "\e[1;2P" instead of "\eO2P" by default.) * Merge patches: https://bitbucket.org/arakiken/mlterm/pull-requests/3/update-a-left-old-code-about-the * Bug fixes: Fix a bug which disabled to assign keypad keys in ~/.mlterm/shortcut. Fix wrong processing of percentage in a font name on framebuffer and wayland. Fix alpha blending in drawing glyphs on wayland. Fix disappearance of the cursor if built with --enable-vt52 option. Fix a bug which shows wrong window title in a splited screen. Fix faulty drawing a wall picture in closing one of splitted screens. Fix segfault when mlterm exits after having reconnected to ssh server automatically. Fix segfault in using input method plugins (except ibus) on wayland. Fix unexpected fallback to "DEFAULT" font in DECDHL or DECDWL lines. Fix screen corruption of libvte compatible library in operating multiple tabs on wayland. Fix segfault on pause or resume on Android. --- Araki Ken ara...@us... |
|
From: Araki K. <ara...@us...> - 2017-07-30 00:23:14
|
Hi, Thanks. Building mlterm without --enable-vt52 option is a workaround to avoid this problem. An attached patch will fix it completely. Regards, --- Araki Ken ara...@us... |
|
From: Araki K. <ara...@us...> - 2017-07-29 04:17:29
|
Hi, From: Vlad <vo...@vo...> Subject: Re: [Mlterm-dev-en] mlterm 3.8.2 released Date: Fri, 28 Jul 2017 15:30:05 +0200 Message-ID: <82c...@vo...> > Cursor is "invisible" in the new version (with 3.8.1 works fine): no > block, no underscore. I've tried -0/-9 options without success. I'd > appreciate any ideas about this. I'm sorry but I haven't reproduced it yet. Please show me options of configure script and ~/.mlterm/main. Regards, --- Araki Ken ara...@us... |
|
From: Vlad <vo...@vo...> - 2017-07-28 13:45:58
|
Hello, Cursor is "invisible" in the new version (with 3.8.1 works fine): no block, no underscore. I've tried -0/-9 options without success. I'd appreciate any ideas about this. Thank you in advance, Vlad. On 17/07/17 14:10, Araki Ken via Mlterm-dev-en wrote: > Hi, > > This is to announce the release of mlterm version 3.8.2 > > http://sourceforge.net/projects/mlterm/files/01release/mlterm-3.8.2/mlterm-3.8.2.tar.gz/download > > SHA1 (mlterm-3.8.2.tar.gz) = 55857697736a62aef4cb29505fb13ae701e4b395 > > Overview of changes from 3.8.1 > =============================== > ver 3.8.2 > * Support page of VT400 or later. (NP, PP, PPA, PPR, PPB, DECCRA and DECLRP) > * Support DECRQDE, DECSCUSR(Ps = 3,4,5,6), DECATC, DECRQM, DECRQMH, DECSCA, > DECERA, DECSEL and DECSED. > * Support SGR of DECRQSS. > * Support MC and DECMC which output screen contents to ~/.mlterm/[tty]-YYYYMMDDHHMMSS.snp. > * Add "baseline_offset" / --blpos option. > * Revive iiimf input method plugin. > (--disable-iiimf optoin of configure script disables this feature.) > * Update unicode property table (generated from UnicodeData.txt and > EastAsianWidth.txt) to version 10.0.0. > * Support brltty with the use of brlapi library. (Experimental) > (configure with --enable-brlapi option.) > * Enable to build on msys2. > * Support DECDHL and DECDWL on console. > * libvte compatible library supports vte 0.48.0 API. > * Bug fixes: > Fix unexpected blocking in exiting mlterm.jar. > Fix a redrawing problem in inserting RTL characters between LTR ones or vice-versa. > Fix unexpected erasing of DECIC and DECDC. > Fix a bug which occupies 100% of CPU in switching mlterm-fb to an inactive > console on linux. > Fix freeze in copy&paste between windows of libvte compatible library. > <dev> in OSC 5379;<dev>:a=b works. > > --- > Araki Ken > ara...@us... > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Mlterm-dev-en mailing list > Mlt...@li... > https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en |
|
From: Araki K. <ara...@us...> - 2017-07-17 12:42:37
|
Hi, This is to announce the release of mlterm version 3.8.2 http://sourceforge.net/projects/mlterm/files/01release/mlterm-3.8.2/mlterm-3.8.2.tar.gz/download SHA1 (mlterm-3.8.2.tar.gz) = 55857697736a62aef4cb29505fb13ae701e4b395 Overview of changes from 3.8.1 =============================== ver 3.8.2 * Support page of VT400 or later. (NP, PP, PPA, PPR, PPB, DECCRA and DECLRP) * Support DECRQDE, DECSCUSR(Ps = 3,4,5,6), DECATC, DECRQM, DECRQMH, DECSCA, DECERA, DECSEL and DECSED. * Support SGR of DECRQSS. * Support MC and DECMC which output screen contents to ~/.mlterm/[tty]-YYYYMMDDHHMMSS.snp. * Add "baseline_offset" / --blpos option. * Revive iiimf input method plugin. (--disable-iiimf optoin of configure script disables this feature.) * Update unicode property table (generated from UnicodeData.txt and EastAsianWidth.txt) to version 10.0.0. * Support brltty with the use of brlapi library. (Experimental) (configure with --enable-brlapi option.) * Enable to build on msys2. * Support DECDHL and DECDWL on console. * libvte compatible library supports vte 0.48.0 API. * Bug fixes: Fix unexpected blocking in exiting mlterm.jar. Fix a redrawing problem in inserting RTL characters between LTR ones or vice-versa. Fix unexpected erasing of DECIC and DECDC. Fix a bug which occupies 100% of CPU in switching mlterm-fb to an inactive console on linux. Fix freeze in copy&paste between windows of libvte compatible library. <dev> in OSC 5379;<dev>:a=b works. --- Araki Ken ara...@us... |
|
From: Araki K. <ara...@us...> - 2017-06-04 14:09:13
|
Hi, From: Didier Spaier <di...@sl...> Subject: Re: [Mlterm-dev-en] Input buffered in mlterm-fb? Date: Thu, 18 May 2017 00:35:31 +0200 Message-ID: <aef...@sl...> > I can't comment on that brltty by lack of knowledge but as per my above > testing report the issue existq even when the brltty daemon is not > started. > > Also, I have a blind friend who helps me for testing but he only uses the > output of his Braille display: he reads with the fingers, do not use > speech synthesis, and do not use a Braille keyboard but a regular one. > > I will have to investigate further anyway if we want to help blind people > speaking one of the CJK languages, so let's concentrate on that later. I've tried to support brltty with the use of brlapi library. I have no confidence but I commit experimental code to hg head. http://bitbucket.org/arakiken/mlterm/get/tip.tar.gz See http://bitbucket.org/arakiken/mlterm/src/tip/doc/en/README.brltty for installation and usage. Regards, --- Araki Ken ara...@us... |
|
From: Araki K. <ara...@us...> - 2017-05-28 04:46:22
|
Hi,
From: Didier Spaier <di...@sl...>
Subject: Re: [Mlterm-dev-en] Input buffered in mlterm-fb?
Date: Thu, 25 May 2017 12:33:10 +0200
Message-ID: <f72...@sl...>
> It seems that I get a permission denied.
>
> I ran this with KBD_INPUT_NAME unset:
> strace -o strace.log mlterm-fb --logseq=true.
>
> This time I got the keyboard working!
> I dn't know if that can give some clue to investigate, but
> I have the vague idea that using strace prevented mlterm-fb
> to send "something" to the tty that somehow would "trap" the output.
>
> I also saw that if I just type:
> strace mlterm-fb
> and then killall either strace or mlterm-fb from another tty,
> I can't get display of input back (although input works)
> even after "setterm --reset".
>
> Anyway:
> didier[~/.mlterm]$ cat msg.log
> May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/event0.
> May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/event11.
> May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/mice.
> May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/mouse0.
> May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/event0.
> May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/event11.
> May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/mice.
> May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/mouse0.
> May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/event0.
> May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/event11.
> May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/mice.
> May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/mouse0.
> didier[~/.mlterm]$
mlterm-fb gets root user's permission in opening /dev/input/event*.
(Permission of mlterm-fb binary is "-rwsr-xr-x")
^
"Permission denied" error above is caused by strace which prevents mlterm-fb
to get root user's permission.
In this case mlterm-fb falls back to reading *stdin* (which is also caused by
KBD_INPUT_NUM=-1) instead of /dev/input/event*, and keyboard input becomes available.
Anyway, I haven't hit unpon yet why nothing comes from /dev/input/event*.
> Incidentally:
> didier[~/.mlterm]$ grep ENOENT strace.log
> access("/etc/suid-debug", F_OK) = -1 ENOENT (No such file or directory)
> access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/tls/x86_64/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> stat("/usr/local/lib/tls/x86_64", 0x7ffedbd1f130) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/tls/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> stat("/usr/local/lib/tls", 0x7ffedbd1f130) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/x86_64/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> stat("/usr/local/lib/x86_64", 0x7ffedbd1f130) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libpobl.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libmef.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libutempter.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libutil.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libfontconfig.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libharfbuzz.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libglib-2.0.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libfreetype.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libbz2.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libpng16.so.16", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libz.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libm.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libexpat.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/lib64/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f700) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f6b0) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f680) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f580) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f660) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f660) = -1 ENOENT (No such file or directory)
> open("/sys/class/input/input2/name", O_RDONLY) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f790) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libfribidi.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
> connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libnsl.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libnss_nis.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/local/lib/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> stat("/home/didier/.config/mlterm", 0x7ffedbd1f6e0) = -1 ENOENT (No such file or directory)
> didier[~/.mlterm]$
>
> This raise some questions:
> 1) I built mlterm-fb with this configure option
> --libdir=/usr/lib64
> Would it be possible and advisable to give this information as a run-time option
> or a parameter to mlterm? I ask because maybe that would avoid some useless
> calls (even if maybe not that costly).
As far as I see http://slint.fr/testing/mlterm/strace.log,
ld.so loads /usr/lib64/libmlterm_coreotl.so and so on finally,
so ld.so is informed of '--libdir=/usr/lib64' correctly by compiling
mlterm-fb with rpath option.
But I'm not familiar to how ld.so searches dynamic link libraries in detail, sorry.
> 2) I didn't see mentioned ~/.config/mlterm in the docs, only ~/.mlterm
> What is that for? Maybe I missed something.
This is undocumented feature.
If ~/.config/mlterm exists, mlterm reads ~/.config/mlterm/* config files instead of
~/.mlterm/*.
mlterm doesn't access config files often, so its cost is ignorable.
Regards,
---
Araki Ken
ara...@us...
|
|
From: Didier S. <di...@sl...> - 2017-05-25 10:33:23
|
Hi, Le 23/05/2017 à 15:20, Araki Ken a écrit : > From: Didier Spaier <di...@sl...> >> As expected setting KBD_INPUT_NUM a to a non-existent <num> throws an >> error: >> ERROR(No such file or directory): Couldn't open /dev/input/event<num> >> but in many cases doesn't prevent the keyboard to work. I am still >> puzzled. I had a look to uitoolkit/fb/ui_display_linux.c, alas I am not a >> developer and don't understand what I read. >> >> 2) thest after having plugged off, then on the optical mouse and plugged >> in an external USB keyboard. > > mlterm-fb reads stdin instead of /dev/input/event* if opening /dev/input/event* > fails or KBD_INPUT_NUM=-1. > The mode of reading stdin disables mlterm-fb to distinguish modifier keys etc, > so mlterm-fb prefers /dev/input/event* to stdin. > > BTW, I'm sorry but I doesn't hit upon the reason why nothing comes from /dev/input/event0. It seems that I get a permission denied. I ran this with KBD_INPUT_NAME unset: strace -o strace.log mlterm-fb --logseq=true. This time I got the keyboard working! I dn't know if that can give some clue to investigate, but I have the vague idea that using strace prevented mlterm-fb to send "something" to the tty that somehow would "trap" the output. I also saw that if I just type: strace mlterm-fb and then killall either strace or mlterm-fb from another tty, I can't get display of input back (although input works) even after "setterm --reset". Anyway: didier[~/.mlterm]$ cat msg.log May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/event0. May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/event11. May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/mice. May 25 11:39:17[6665] ERROR(Permission denied): Couldn't open /dev/input/mouse0. May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/event0. May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/event11. May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/mice. May 25 12:00:19[7075] ERROR(Permission denied): Couldn't open /dev/input/mouse0. May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/event0. May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/event11. May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/mice. May 25 12:01:40[7137] ERROR(Permission denied): Couldn't open /dev/input/mouse0. didier[~/.mlterm]$ didier[~/.mlterm]$ cat pts_0.log didier[~/.mlterm]$ ls aafont aafont.bak bad challenge color font font-fb font-fb.bak key main msg.log pts_0.log strace.log taafont termcap tfont vaafont vfont xim didier[~/.mlterm]$ exit didier[~/.mlterm]$ (I just typed "ls" while in mlterm-fb so this output was expected) as strace.log is big I uploaded it here: http://slint.fr/testing/mlterm/strace.log Incidentally: didier[~/.mlterm]$ grep ENOENT strace.log access("/etc/suid-debug", F_OK) = -1 ENOENT (No such file or directory) access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/usr/local/lib/tls/x86_64/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/local/lib/tls/x86_64", 0x7ffedbd1f130) = -1 ENOENT (No such file or directory) open("/usr/local/lib/tls/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/local/lib/tls", 0x7ffedbd1f130) = -1 ENOENT (No such file or directory) open("/usr/local/lib/x86_64/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/local/lib/x86_64", 0x7ffedbd1f130) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libmlterm_coreotl.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libpobl.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libmef.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libutempter.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libutil.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libfontconfig.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libharfbuzz.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libglib-2.0.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libfreetype.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libbz2.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libpng16.so.16", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libz.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libm.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libexpat.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f700) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f6b0) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f680) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f580) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f660) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f660) = -1 ENOENT (No such file or directory) open("/sys/class/input/input2/name", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f790) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libfribidi.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libnsl.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libnss_nis.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/home/didier/.config/mlterm", 0x7ffedbd1f6e0) = -1 ENOENT (No such file or directory) didier[~/.mlterm]$ This raise some questions: 1) I built mlterm-fb with this configure option --libdir=/usr/lib64 Would it be possible and advisable to give this information as a run-time option or a parameter to mlterm? I ask because maybe that would avoid some useless calls (even if maybe not that costly). 2) I didn't see mentioned ~/.config/mlterm in the docs, only ~/.mlterm What is that for? Maybe I missed something. >> Issue #2: >> >> If I start mlterm-fb say from /dev/tty2 then switch to an X display with >> Ctrl+Alt+F7, the Xserver having been started on /dev/tty1 for instance, >> this result in mlterm using 100% of one of my 4 CPU cores. >> >> As son as I switch back to /dev/pts/2 (whre mlter-fb is running) this >> percentage decreases to a (expected) very low value as expected. But I >> for instance I switch to /dev/tty3, the CPU% increases again and if >> htop is running in /dev/pts/2 artefacts from the display in /dev/pts/2 >> appear in /dev/tty3. I have no idea why. >> >> Issue #3 >> >> I observed that using the 'dialog' program in mlterm, if used without the >> "--colors=false" options triggers errors shown in the attached file >> debuglog, altough the output seems OK. This occurs under X as well as in >> a framebuffer. >> >> I attach also the displayed dialog (under X) and two output of the ANSI >> sequences displaying it, one in raw and the other in ttyrec formats, both >> in a framebuffer. The displayed dialog is the same under X or in a >> framebuffer. > > Thanks, please test an attached patch (which has been already committed to hg head) > It will fix these problem. Yes it did fix them, thanks! regards, Didier |
|
From: Araki K. <ara...@us...> - 2017-05-23 13:19:31
|
Hi, From: Didier Spaier <di...@sl...> Subject: Re: [Mlterm-dev-en] Input buffered in mlterm-fb? Date: Thu, 18 May 2017 00:35:31 +0200 Message-ID: <aef...@sl...> > Anyway I don't think that brltty comes into play in the issue. I made > more tests without it: > > 1) tests with just the intagrated keyboard of my laptop and an optical > USB mouse pluged in. > > didier[~]$ for f in /sys/class/input/input*/name; do printf $f|sed 's,[^[:digit:]]*,,;s,/.*,,'; printf " ";cat $f; done|sort -g > 0 AT Translated Set 2 keyboard > 1 Speakup > 3 Lid Switch > 4 Sleep Button > 5 Power Button > 6 ThinkPad Extra Buttons > 8 HDA Intel PCH Mic > 9 HDA Intel PCH Dock Mic > 10 HDA Intel PCH Dock Headphone > 11 HDA Intel PCH Headphone > 12 Video Bus > 16 Logitech USB Optical Mouse > didier[~]$ > > Value of KBD_INPUT_NUM with which the keyboard works > -1 > 1 > 11 > 12 > 14 > 15 > 16 > 17 > 18 > 19 > 20 > > As expected setting KBD_INPUT_NUM a to a non-existent <num> throws an > error: > ERROR(No such file or directory): Couldn't open /dev/input/event<num> > but in many cases doesn't prevent the keyboard to work. I am still > puzzled. I had a look to uitoolkit/fb/ui_display_linux.c, alas I am not a > developer and don't understand what I read. > > 2) thest after having plugged off, then on the optical mouse and plugged > in an external USB keyboard. mlterm-fb reads stdin instead of /dev/input/event* if opening /dev/input/event* fails or KBD_INPUT_NUM=-1. The mode of reading stdin disables mlterm-fb to distinguish modifier keys etc, so mlterm-fb prefers /dev/input/event* to stdin. BTW, I'm sorry but I doesn't hit upon the reason why nothing comes from /dev/input/event0. > didier[~]$ for f in /sys/class/input/input*/name; do printf $f|sed 's,[^[:digit:]]*,,;s,/.*,,'; printf " ";cat $f; done|sort -g > 0 AT Translated Set 2 keyboard > 1 Speakup > 3 Lid Switch > 4 Sleep Button > 5 Power Button > 6 ThinkPad Extra Buttons > 8 HDA Intel PCH Mic > 9 HDA Intel PCH Dock Mic > 10 HDA Intel PCH Dock Headphone > 11 HDA Intel PCH Headphone > 12 Video Bus > 22 Logitech USB Optical Mouse > 23 BTC USB Multimedia Keyboard > 24 BTC USB Multimedia Keyboard > didier[~]$ > > Value of KBD_INPUT_NUM with which at least one keyboard works: > -1 Integrated keyboard > 1 Integrated keyboard > 14 thru 30 Both keyboards > I assume that all values > 14 are OK > Very big values (100, 1000, 9999999) Both keyboards > > These results look similar to those from the first tests. I'm confused. I have no idea why KBD_INPUT_NUM=-1 results in "Integrated keyboard" while KBD_INPUT_NUM=14 thru 30 results in "Both keyboards". > Issue #2: > > If I start mlterm-fb say from /dev/tty2 then switch to an X display with > Ctrl+Alt+F7, the Xserver having been started on /dev/tty1 for instance, > this result in mlterm using 100% of one of my 4 CPU cores. > > As son as I switch back to /dev/pts/2 (whre mlter-fb is running) this > percentage decreases to a (expected) very low value as expected. But I > for instance I switch to /dev/tty3, the CPU% increases again and if > htop is running in /dev/pts/2 artefacts from the display in /dev/pts/2 > appear in /dev/tty3. I have no idea why. > > Issue #3 > > I observed that using the 'dialog' program in mlterm, if used without the > "--colors=false" options triggers errors shown in the attached file > debuglog, altough the output seems OK. This occurs under X as well as in > a framebuffer. > > I attach also the displayed dialog (under X) and two output of the ANSI > sequences displaying it, one in raw and the other in ttyrec formats, both > in a framebuffer. The displayed dialog is the same under X or in a > framebuffer. Thanks, please test an attached patch (which has been already committed to hg head) It will fix these problem. Regards, --- Araki Ken ara...@us... |
|
From: Didier S. <di...@sl...> - 2017-05-20 20:55:53
|
Hi, I resend this message without the attachments now stored in http://slint.fr/testing/mlterm/ as it has been held until now for this reason: Message body is too big: 170941 bytes with a limit of 40 KB Fortunately it will go through this time. Regards, Didier -------- Message transféré -------- Sujet : Re: [Mlterm-dev-en] Input buffered in mlterm-fb? Date : Thu, 18 May 2017 00:35:31 +0200 De : Didier Spaier <di...@sl...> Pour : mlt...@li... Hi, in this message I will answer your last post but also bring other issues. I hope this is acceptable. Le 13/05/2017 à 19:59, Araki Ken a écrit : > From: Didier Spaier <di...@sl...> >> Le 08/05/2017 à 18:30, Araki Ken a écrit : >> I already checked, but here goes: >> >> didier[~]$ for f in * ; do echo $f; cat $f; done >> 0 >> AT Translated Set 2 keyboard >> 1 >> Speakup >> 10 >> HDA Intel PCH Headphone >> 11 >> Video Bus >> 12 >> Logitech USB Optical Mouse >> 13 >> BRLTTY 5.4 Linux Screen Driver Keyboard >> 3 >> Lid Switch >> 4 >> Sleep Button >> 5 >> Power Button >> 6 >> ThinkPad Extra Buttons >> 7 >> HDA Intel PCH Mic >> 8 >> HDA Intel PCH Dock Mic >> 9 >> HDA Intel PCH Dock Headphone > > How about starting mlterm-fb with 13 > > If it solves the problem, I'll fix mlterm-fb to prefer BRLTTY keyboard to > normal AT keyboard. It didn't work Anyway I don't think that brltty comes into play in the issue. I made more tests without it: 1) tests with just the intagrated keyboard of my laptop and an optical USB mouse pluged in. didier[~]$ for f in /sys/class/input/input*/name; do printf $f|sed 's,[^[:digit:]]*,,;s,/.*,,'; printf " ";cat $f; done|sort -g 0 AT Translated Set 2 keyboard 1 Speakup 3 Lid Switch 4 Sleep Button 5 Power Button 6 ThinkPad Extra Buttons 8 HDA Intel PCH Mic 9 HDA Intel PCH Dock Mic 10 HDA Intel PCH Dock Headphone 11 HDA Intel PCH Headphone 12 Video Bus 16 Logitech USB Optical Mouse didier[~]$ Value of KBD_INPUT_NUM with which the keyboard works -1 1 11 12 14 15 16 17 18 19 20 As expected setting KBD_INPUT_NUM a to a non-existent <num> throws an error: ERROR(No such file or directory): Couldn't open /dev/input/event<num> but in many cases doesn't prevent the keyboard to work. I am still puzzled. I had a look to uitoolkit/fb/ui_display_linux.c, alas I am not a developer and don't understand what I read. 2) thest after having plugged off, then on the optical mouse and plugged in an external USB keyboard. didier[~]$ for f in /sys/class/input/input*/name; do printf $f|sed 's,[^[:digit:]]*,,;s,/.*,,'; printf " ";cat $f; done|sort -g 0 AT Translated Set 2 keyboard 1 Speakup 3 Lid Switch 4 Sleep Button 5 Power Button 6 ThinkPad Extra Buttons 8 HDA Intel PCH Mic 9 HDA Intel PCH Dock Mic 10 HDA Intel PCH Dock Headphone 11 HDA Intel PCH Headphone 12 Video Bus 22 Logitech USB Optical Mouse 23 BTC USB Multimedia Keyboard 24 BTC USB Multimedia Keyboard didier[~]$ Value of KBD_INPUT_NUM with which at least one keyboard works: -1 Integrated keyboard 1 Integrated keyboard 14 thru 30 Both keyboards I assume that all values > 14 are OK Very big values (100, 1000, 9999999) Both keyboards These results look similar to those from the first tests. >> Which leads to an off topic question. nosh is supposed to be able >> to provide two outputs if I understand well: one to draw a framebuffer >> and another to provide discrete characters that can be read by brltty. >> Can mlterm do something similar[1]? Cf: >> https://jdebp.eu/Softwares/nosh/brltty.html >> https://jdebp.eu/Softwares/nosh/user-vt-screenshots.html > > I'm not familiar to brltty and nosh at all. > > As far as I looked over them, it seems possible to enable mlterm to > output characters to brltty, though I haven't understand yet the natural > way of processing characters to be output to brltty. > > http://mlterm.sf.net/mlterm-3.8.1-brltty.patch is a simple patch, and > I tested brltty as follows. > > $ tar xzvf mlterm-3.8.1.tar.gz > $ cd mlterm-3.8.1 > $ patch -p1 < mlterm-3.8.1-brltty.patch > $ ./configure ... > $ make; sudo make install > $ export BRLTTY_SPEECH_INPUT=~/tmp_fifo > $ brltty -s es -E > $ mlterm I can't comment on that brltty by lack of knowledge but as per my above testing report the issue existq even when the brltty daemon is not started. Also, I have a blind friend who helps me for testing but he only uses the output of his Braille display: he reads with the fingers, do not use speech synthesis, and do not use a Braille keyboard but a regular one. I will have to investigate further anyway if we want to help blind people speaking one of the CJK languages, so let's concentrate on that later. --- Issue #2: If I start mlterm-fb say from /dev/tty2 then switch to an X display with Ctrl+Alt+F7, the Xserver having been started on /dev/tty1 for instance, this result in mlterm using 100% of one of my 4 CPU cores. As son as I switch back to /dev/pts/2 (whre mlter-fb is running) this percentage decreases to a (expected) very low value as expected. But I for instance I switch to /dev/tty3, the CPU% increases again and if htop is running in /dev/pts/2 artefacts from the display in /dev/pts/2 appear in /dev/tty3. I have no idea why. --- Issue #3 I observed that using the 'dialog' program in mlterm, if used without the "--colors=false" options triggers errors shown in the attached file debuglog, altough the output seems OK. This occurs under X as well as in a framebuffer. I attach also the displayed dialog (under X) and two output of the ANSI sequences displaying it, one in raw and the other in ttyrec formats, both in a framebuffer. The displayed dialog is the same under X or in a framebuffer. --- Please feel free to request any information and testing that could help you investigate these issues and thanks for your time. Best regards, Didier |
|
From: Araki K. <ara...@us...> - 2017-05-18 15:49:38
|
Hi,
From: Vlad <vo...@vo...>
Subject: Re: [Mlterm-dev-en] freetype 2.8.* glitches
Date: Wed, 17 May 2017 17:34:06 +0200
Message-ID: <2d2...@vo...>
> > Does an attached patch improve this symptoms ?
> > Please test it.
> Apparently the patch solves the problem. Thanks for the quick replay!
I've added "baseline_offset" option ("--blpos" in command line) to hg head.
Start mlterm (3.8.2 or later) with "--blpos -1" option in such a situation.
Regards,
---
Araki Ken
ara...@us...
|
|
From: Didier S. <di...@sl...> - 2017-05-17 22:35:50
|
Hi, in this message I will answer your last post but also bring other issues. I hope this is acceptable. Le 13/05/2017 à 19:59, Araki Ken a écrit : > From: Didier Spaier <di...@sl...> >> Le 08/05/2017 à 18:30, Araki Ken a écrit : >> I already checked, but here goes: >> >> didier[~]$ for f in * ; do echo $f; cat $f; done >> 0 >> AT Translated Set 2 keyboard >> 1 >> Speakup >> 10 >> HDA Intel PCH Headphone >> 11 >> Video Bus >> 12 >> Logitech USB Optical Mouse >> 13 >> BRLTTY 5.4 Linux Screen Driver Keyboard >> 3 >> Lid Switch >> 4 >> Sleep Button >> 5 >> Power Button >> 6 >> ThinkPad Extra Buttons >> 7 >> HDA Intel PCH Mic >> 8 >> HDA Intel PCH Dock Mic >> 9 >> HDA Intel PCH Dock Headphone > > How about starting mlterm-fb with 13 > > If it solves the problem, I'll fix mlterm-fb to prefer BRLTTY keyboard to > normal AT keyboard. It didn't work Anyway I don't think that brltty comes into play in the issue. I made more tests without it: 1) tests with just the intagrated keyboard of my laptop and an optical USB mouse pluged in. didier[~]$ for f in /sys/class/input/input*/name; do printf $f|sed 's,[^[:digit:]]*,,;s,/.*,,'; printf " ";cat $f; done|sort -g 0 AT Translated Set 2 keyboard 1 Speakup 3 Lid Switch 4 Sleep Button 5 Power Button 6 ThinkPad Extra Buttons 8 HDA Intel PCH Mic 9 HDA Intel PCH Dock Mic 10 HDA Intel PCH Dock Headphone 11 HDA Intel PCH Headphone 12 Video Bus 16 Logitech USB Optical Mouse didier[~]$ Value of KBD_INPUT_NUM with which the keyboard works -1 1 11 12 14 15 16 17 18 19 20 As expected setting KBD_INPUT_NUM a to a non-existent <num> throws an error: ERROR(No such file or directory): Couldn't open /dev/input/event<num> but in many cases doesn't prevent the keyboard to work. I am still puzzled. I had a look to uitoolkit/fb/ui_display_linux.c, alas I am not a developer and don't understand what I read. 2) thest after having plugged off, then on the optical mouse and plugged in an external USB keyboard. didier[~]$ for f in /sys/class/input/input*/name; do printf $f|sed 's,[^[:digit:]]*,,;s,/.*,,'; printf " ";cat $f; done|sort -g 0 AT Translated Set 2 keyboard 1 Speakup 3 Lid Switch 4 Sleep Button 5 Power Button 6 ThinkPad Extra Buttons 8 HDA Intel PCH Mic 9 HDA Intel PCH Dock Mic 10 HDA Intel PCH Dock Headphone 11 HDA Intel PCH Headphone 12 Video Bus 22 Logitech USB Optical Mouse 23 BTC USB Multimedia Keyboard 24 BTC USB Multimedia Keyboard didier[~]$ Value of KBD_INPUT_NUM with which at least one keyboard works: -1 Integrated keyboard 1 Integrated keyboard 14 thru 30 Both keyboards I assume that all values > 14 are OK Very big values (100, 1000, 9999999) Both keyboards These results look similar to those from the first tests. >> Which leads to an off topic question. nosh is supposed to be able >> to provide two outputs if I understand well: one to draw a framebuffer >> and another to provide discrete characters that can be read by brltty. >> Can mlterm do something similar[1]? Cf: >> https://jdebp.eu/Softwares/nosh/brltty.html >> https://jdebp.eu/Softwares/nosh/user-vt-screenshots.html > > I'm not familiar to brltty and nosh at all. > > As far as I looked over them, it seems possible to enable mlterm to > output characters to brltty, though I haven't understand yet the natural > way of processing characters to be output to brltty. > > http://mlterm.sf.net/mlterm-3.8.1-brltty.patch is a simple patch, and > I tested brltty as follows. > > $ tar xzvf mlterm-3.8.1.tar.gz > $ cd mlterm-3.8.1 > $ patch -p1 < mlterm-3.8.1-brltty.patch > $ ./configure ... > $ make; sudo make install > $ export BRLTTY_SPEECH_INPUT=~/tmp_fifo > $ brltty -s es -E > $ mlterm I can't comment on that brltty by lack of knowledge but as per my above testing report the issue existq even when the brltty daemon is not started. Also, I have a blind friend who helps me for testing but he only uses the output of his Braille display: he reads with the fingers, do not use speech synthesis, and do not use a Braille keyboard but a regular one. I will have to investigate further anyway if we want to help blind people speaking one of the CJK languages, so let's concentrate on that later. --- Issue #2: If I start mlterm-fb say from /dev/tty2 then switch to an X display with Ctrl+Alt+F7, the Xserver having been started on /dev/tty1 for instance, this result in mlterm using 100% of one of my 4 CPU cores. As son as I switch back to /dev/pts/2 (whre mlter-fb is running) this percentage decreases to a (expected) very low value as expected. But I for instance I switch to /dev/tty3, the CPU% increases again and if htop is running in /dev/pts/2 artefacts from the display in /dev/pts/2 appear in /dev/tty3. I have no idea why. --- Issue #3 I observed that using the 'dialog' program in mlterm, if used without the "--colors=false" options triggers errors shown in the attached file debuglog, altough the output seems OK. This occurs under X as well as in a framebuffer. I attach also the displayed dialog (under X) and two output of the ANSI sequences displaying it, one in raw and the other in ttyrec formats, both in a framebuffer. The displayed dialog is the same under X or in a framebuffer. --- Please feel free to request any information and testing that could help you investigate these issues and thanks for your time. Best regards, Didier |
|
From: Vlad <vo...@vo...> - 2017-05-17 15:34:49
|
On 17/05/17 16:37, Araki Ken wrote: > Hi, > > From: Vlad <vo...@vo...> > Subject: [Mlterm-dev-en] freetype 2.8.* glitches > Date: Wed, 17 May 2017 13:01:24 +0200 > Message-ID: <43572e7b-a466-3d0a-06c7-9ecab0086968@net.home> > >> I've recently updated freetype 2.7.x -> 2.8.2 and noticed some glitches. >> For example underscore isn't visible. In de current directory I have two >> files "test_1" "test_2", but if I do simple ls, I can't see the >> underscore, so it looks like "test 1" "test 2". If I try to select >> these files name in mlterm, I see the underscores again... I'd >> appreciate any thoughts about this issue. My mlterm-3.8.1 config is below: >> use_transbg = true >> wall_picture = >> logsize = 512 >> fontsize = 13 >> type_engine = xft >> scrollbar_mode = none >> use_clipboard = true >> use_variable_column_width = true >> termtype = mlterm-256color >> input_method = none >> col_size_of_width_a = 1 >> use_dynamic_comb = false >> receive_string_via_ucs = true >> use_multi_column_char = true >> use_bidi = false >> mod_meta_mode = esc >> use_combining = true >> compose_dec_special_font = true >> use_ansi_colors = true >> only_use_unicode_font = true >> box_drawing_font = decsp >> regard_uri_as_word = true > Does an attached patch improve this symptoms ? > Please test it. > --- > Araki Ken > ara...@us... Apparently the patch solves the problem. Thanks for the quick replay! Regards, Vlad. |
|
From: Araki K. <ara...@us...> - 2017-05-17 14:37:26
|
Hi, From: Vlad <vo...@vo...> Subject: [Mlterm-dev-en] freetype 2.8.* glitches Date: Wed, 17 May 2017 13:01:24 +0200 Message-ID: <43572e7b-a466-3d0a-06c7-9ecab0086968@net.home> > I've recently updated freetype 2.7.x -> 2.8.2 and noticed some glitches. > For example underscore isn't visible. In de current directory I have two > files "test_1" "test_2", but if I do simple ls, I can't see the > underscore, so it looks like "test 1" "test 2". If I try to select > these files name in mlterm, I see the underscores again... I'd > appreciate any thoughts about this issue. My mlterm-3.8.1 config is below: > use_transbg = true > wall_picture = > logsize = 512 > fontsize = 13 > type_engine = xft > scrollbar_mode = none > use_clipboard = true > use_variable_column_width = true > termtype = mlterm-256color > input_method = none > col_size_of_width_a = 1 > use_dynamic_comb = false > receive_string_via_ucs = true > use_multi_column_char = true > use_bidi = false > mod_meta_mode = esc > use_combining = true > compose_dec_special_font = true > use_ansi_colors = true > only_use_unicode_font = true > box_drawing_font = decsp > regard_uri_as_word = true Does an attached patch improve this symptoms ? Please test it. --- Araki Ken ara...@us... |
|
From: Vlad <vo...@vo...> - 2017-05-17 13:46:54
|
On 17/05/17 13:32, Ian D. Leroux wrote:
> On Wed, 17 May 2017 13:01:24 +0200 Vlad <vo...@vo...> wrote:
>> I've recently updated freetype 2.7.x -> 2.8.2 and noticed some
>> glitches. For example underscore isn't visible. In de current
>> directory I have two files "test_1" "test_2", but if I do simple ls,
>> I can't see the underscore, so it looks like "test 1" "test 2".
> Possibly related: yesterday I noticed that the character "4" was
> invisible in my mlterm ("3" showed up fine). Starting a fresh mlterm
> process made the symptom go away, so this looks like an intermittent
> glitch in the initialization of a glyph table somewhere.
For me that wasn't the case. I rebooted the machine, but had this issue
anyway.
>
> mlterm-3.8.1,
>
> $ cat .mlterm/main
> bel_mode = visual
> fade_ratio = 95
> geometry=80x32-0-0
> regard_uri_as_word = true
> termtype = mlterm
> use_scrollbar = false
>
> fg_color = rgb:00/00/00
> bg_color = rgb:ff/ff/ff
> fontsize = 14
>
> --
> IDL
|
|
From: Ian D. L. <idl...@fa...> - 2017-05-17 11:32:39
|
On Wed, 17 May 2017 13:01:24 +0200 Vlad <vo...@vo...> wrote:
> I've recently updated freetype 2.7.x -> 2.8.2 and noticed some
> glitches. For example underscore isn't visible. In de current
> directory I have two files "test_1" "test_2", but if I do simple ls,
> I can't see the underscore, so it looks like "test 1" "test 2".
Possibly related: yesterday I noticed that the character "4" was
invisible in my mlterm ("3" showed up fine). Starting a fresh mlterm
process made the symptom go away, so this looks like an intermittent
glitch in the initialization of a glyph table somewhere.
mlterm-3.8.1,
$ cat .mlterm/main
bel_mode = visual
fade_ratio = 95
geometry=80x32-0-0
regard_uri_as_word = true
termtype = mlterm
use_scrollbar = false
fg_color = rgb:00/00/00
bg_color = rgb:ff/ff/ff
fontsize = 14
--
IDL
|
|
From: Vlad <vo...@vo...> - 2017-05-17 11:17:13
|
Hello, I've recently updated freetype 2.7.x -> 2.8.2 and noticed some glitches. For example underscore isn't visible. In de current directory I have two files "test_1" "test_2", but if I do simple ls, I can't see the underscore, so it looks like "test 1" "test 2". If I try to select these files name in mlterm, I see the underscores again... I'd appreciate any thoughts about this issue. My mlterm-3.8.1 config is below: use_transbg = true wall_picture = logsize = 512 fontsize = 13 type_engine = xft scrollbar_mode = none use_clipboard = true use_variable_column_width = true termtype = mlterm-256color input_method = none col_size_of_width_a = 1 use_dynamic_comb = false receive_string_via_ucs = true use_multi_column_char = true use_bidi = false mod_meta_mode = esc use_combining = true compose_dec_special_font = true use_ansi_colors = true only_use_unicode_font = true box_drawing_font = decsp regard_uri_as_word = true Thanks in advance, Vlad. P.S. With line_space=1 the problem disappears, but then I see gaps between lines in ASCII art for example. |
|
From: Araki K. <ara...@us...> - 2017-05-13 17:59:14
|
Hi, From: Didier Spaier <di...@sl...> Subject: Re: [Mlterm-dev-en] Input buffered in mlterm-fb? Date: Mon, 8 May 2017 19:24:06 +0200 Message-ID: <5fb...@sl...> > Le 08/05/2017 à 18:30, Araki Ken a écrit : > > If you execute "KBD_INPUT_NUM=0 mlterm-fb" and can't input anything, > > /dev/input/event0 might not be a keyboard device you use. > > Will you inform me of the result of following commands just in case? > > > > $ for f in /sys/class/input/input*/name; do echo $f; cat $f; done > > I already checked, but here goes: > > didier[~]$ for f in /sys/class/input/input*/name; do echo $f; cat $f; done > /sys/class/input/input0/name > AT Translated Set 2 keyboard > /sys/class/input/input1/name > Speakup > /sys/class/input/input10/name > HDA Intel PCH Headphone > /sys/class/input/input11/name > Video Bus > /sys/class/input/input12/name > Logitech USB Optical Mouse > /sys/class/input/input13/name > BRLTTY 5.4 Linux Screen Driver Keyboard > /sys/class/input/input3/name > Lid Switch > /sys/class/input/input4/name > Sleep Button > /sys/class/input/input5/name > Power Button > /sys/class/input/input6/name > ThinkPad Extra Buttons > /sys/class/input/input7/name > HDA Intel PCH Mic > /sys/class/input/input8/name > HDA Intel PCH Dock Mic > /sys/class/input/input9/name > HDA Intel PCH Dock Headphone How about starting mlterm-fb with KBD_INPUT_NUM=13 ? If it solves the problem, I'll fix mlterm-fb to prefer BRLTTY keyboard to normal AT keyboard. > Which leads to an off topic question. nosh is supposed to be able > to provide two outputs if I understand well: one to draw a framebuffer > and another to provide discrete characters that can be read by brltty. > Can mlterm do something similar[1]? Cf: > https://jdebp.eu/Softwares/nosh/brltty.html > https://jdebp.eu/Softwares/nosh/user-vt-screenshots.html I'm not familiar to brltty and nosh at all. As far as I looked over them, it seems possibe to enable mlterm to output characters to brltty, though I haven't understand yet the natural way of processing characters to be output to brltty. http://mlterm.sf.net/mlterm-3.8.1-brltty.patch is a simple patch, and I tested brltty as follows. $ tar xzvf mlterm-3.8.1.tar.gz $ cd mlterm-3.8.1 $ patch -p1 < mlterm-3.8.1-brltty.patch $ ./configure ... $ make; sudo make install $ export BRLTTY_SPEECH_INPUT=~/tmp_fifo $ brltty -s es -E $ mlterm I haven't try nosh yet. I'll investigate this topic a bit more. Regards, --- Araki Ken ara...@us... |
545 messages has been excluded from this view by a project administrator.
