mlterm-dev-en — mlterm mailing list(English)

Re: [Mlterm-dev-en] Reproducible crash with OTL

[Ian D. L. <idl...@fa...>]

On Wed, 06 Apr 2016 21:16:53 +0900 (JST) Araki Ken
<ara...@us...> wrote:
>  I think http://mlterm.sf.net/mlterm-3.7.0-fixsegfault.patch fixes
> this problem.

Confirmed, with that patch I no longer see the segfault.  Thanks for
the quick fix!

--
IDL

Re: [Mlterm-dev-en] Using multiple unicode fonts in mlterm

[Araki K. <ara...@us...>]

 Hi,

From: "Ian D. Leroux" <idl...@fa...>
Subject: [Mlterm-dev-en] Using multiple unicode fonts in mlterm
Date: Tue, 5 Apr 2016 22:02:10 +0200
Message-ID: <201...@fa...>

> One of the features I find exciting about mlterm is the option to
> specify which fonts to use for different unicode ranges, rather than
> relying on fontconfig's automatic fallback mechanism.  I'm not sure
> that I understand how this works though.  As an (admittedly silly)
> test case, consider the following .mlterm/aafont setting:
> 
> DEFAULT=DejaVu Sans Mono
> U+00-ff=Terminus
> 
> I would expect this to use Terminus for the first 255 code points and
> DejaVu for higher codepoints.  In fact it uses DejaVu for the ASCII
> characters, and Terminus only for characters in the f0-ff range (such
> as 'é', U+00E9).

 It is not supported to specify which font to use for U+00-7f for now.
 A font specified as DEFAULT or ISO10646_UCS4_1 is used to show U+00-7f characters.

 I'll add this limitation to the man page.

> On the other hand, if I set
> 
> DEFAULT=DejaVu Sans Mono
> U+f0-ff=Terminus
> 
> (which I would expect to reproduce the behaviour I observed in the
> first case) then Terminus never gets used at all.

 If you use Terminus for U+00E9, specify as follows instead of U+f0-ff.

U+80-ff=Terminus

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

Re: [Mlterm-dev-en] Reproducible crash with OTL

[Araki K. <ara...@us...>]

 Hi,

 Thanks a lot for your report.

 I think http://mlterm.sf.net/mlterm-3.7.0-fixsegfault.patch fixes this problem.

 Regards,

From: "Ian D. Leroux" <idl...@fa...>
Subject: [Mlterm-dev-en] Reproducible crash with OTL
Date: Tue, 5 Apr 2016 08:03:38 +0200
Message-ID: <201...@fa...>

> Greetings, and thanks for your work on mlterm!
> 
> I'm currently testing out mlterm version 3.7.0 on NetBSD-current (on an
> amd64 machine).  My mlterm was built with cairo, fribidi, m17nlib, otl
> and Xft but without gdk_pixbuf or any of the input methods.  I can
> reliably make it segfault by launching nvi(1) and inserting two
> alphabetic characters and a space at the beginning of the buffer.  That
> is, if I try to create a file whose contents are "ab " (or in fact any
> longer word followed by a space), then mlterm crashes when I hit the
> spacebar.  This doesn't happen with the default configuration.  It
> requires that (at least) the following two settings appear in
> ~/.mlterm/main:
> 
> use_ot_layout = true
> termtype = mlterm
> 
> Right now I'm running with only those two settings in main, and no
> other settings files in .mlterm (there are the usual msg.log and
> challenge files).  A backtrace collected after a crash of a binary
> compiled with -g -O2 follows:
> 
> Core was generated by `mlterm'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  ml_char_copy (dst=dst@entry=0x7f7fffffda50, src=0x0) at ml_char.c:662
> 662             memcpy( dst , src , sizeof( ml_char_t)) ;
> (gdb) bt
> #0  ml_char_copy (dst=dst@entry=0x7f7fffffda50, src=0x0) at ml_char.c:662
> #1  0x00000000004171b4 in draw_cursor (screen=screen@entry=0x7f7ff7b3d000)
>     at x_screen.c:606
> #2  0x000000000041aba4 in highlight_cursor (screen=0x7f7ff7b3d000)
>     at x_screen.c:968
> #3  update_window (win=0x7f7ff7b3d000, flag=<optimized out>) at x_screen.c:1597
> #4  0x0000000000410b67 in x_window_update (win=0x7f7ff7b3d000,
>     flag=<optimized out>) at ../xwindow/xlib/x_window.c:2302
> #5  0x00000000004423ef in ml_parse_vt100_sequence (vt100_parser=0x7f7ff7b38800)
>     at ml_vt100_parser.c:7371
> #6  0x000000000040e784 in receive_next_event () at x_event_source.c:281
> #7  x_event_source_process () at x_event_source.c:345
> #8  0x000000000040cf2c in main_loop_start () at main_loop.c:485
> #9  0x000000000044973c in main (argc=1, argv=0x7f7fffffdbd8) at main.c:181
> 
> So somehow mlterm ends up trying to memcpy NULL while redrawing the
> cursor after I hit space.
> 
> What other tests can I run to help narrow down the root cause of the
> problem?
> 
> Thanks for your help,
> 
> --
> IDL
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlt...@li...
>yyyyyyy https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en

[Mlterm-dev-en] Using multiple unicode fonts in mlterm

[Ian D. L. <idl...@fa...>]

One of the features I find exciting about mlterm is the option to
specify which fonts to use for different unicode ranges, rather than
relying on fontconfig's automatic fallback mechanism.  I'm not sure
that I understand how this works though.  As an (admittedly silly)
test case, consider the following .mlterm/aafont setting:

DEFAULT=DejaVu Sans Mono
U+00-ff=Terminus

I would expect this to use Terminus for the first 255 code points and
DejaVu for higher codepoints.  In fact it uses DejaVu for the ASCII
characters, and Terminus only for characters in the f0-ff range (such
as 'é', U+00E9).  On the other hand, if I set

DEFAULT=DejaVu Sans Mono
U+f0-ff=Terminus

(which I would expect to reproduce the behaviour I observed in the
first case) then Terminus never gets used at all.  Am I misinterpreting
the manpage, or are there restrictions on which unicode ranges can have
their fonts set by this mechanism?  I'm curious to understand how this is supposed to work. 

--
IDL

[Mlterm-dev-en] Reproducible crash with OTL

[Ian D. L. <idl...@fa...>]

Greetings, and thanks for your work on mlterm!

I'm currently testing out mlterm version 3.7.0 on NetBSD-current (on an
amd64 machine).  My mlterm was built with cairo, fribidi, m17nlib, otl
and Xft but without gdk_pixbuf or any of the input methods.  I can
reliably make it segfault by launching nvi(1) and inserting two
alphabetic characters and a space at the beginning of the buffer.  That
is, if I try to create a file whose contents are "ab " (or in fact any
longer word followed by a space), then mlterm crashes when I hit the
spacebar.  This doesn't happen with the default configuration.  It
requires that (at least) the following two settings appear in
~/.mlterm/main:

use_ot_layout = true
termtype = mlterm

Right now I'm running with only those two settings in main, and no
other settings files in .mlterm (there are the usual msg.log and
challenge files).  A backtrace collected after a crash of a binary
compiled with -g -O2 follows:

Core was generated by `mlterm'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  ml_char_copy (dst=dst@entry=0x7f7fffffda50, src=0x0) at ml_char.c:662
662             memcpy( dst , src , sizeof( ml_char_t)) ;
(gdb) bt
#0  ml_char_copy (dst=dst@entry=0x7f7fffffda50, src=0x0) at ml_char.c:662
#1  0x00000000004171b4 in draw_cursor (screen=screen@entry=0x7f7ff7b3d000)
    at x_screen.c:606
#2  0x000000000041aba4 in highlight_cursor (screen=0x7f7ff7b3d000)
    at x_screen.c:968
#3  update_window (win=0x7f7ff7b3d000, flag=<optimized out>) at x_screen.c:1597
#4  0x0000000000410b67 in x_window_update (win=0x7f7ff7b3d000,
    flag=<optimized out>) at ../xwindow/xlib/x_window.c:2302
#5  0x00000000004423ef in ml_parse_vt100_sequence (vt100_parser=0x7f7ff7b38800)
    at ml_vt100_parser.c:7371
#6  0x000000000040e784 in receive_next_event () at x_event_source.c:281
#7  x_event_source_process () at x_event_source.c:345
#8  0x000000000040cf2c in main_loop_start () at main_loop.c:485
#9  0x000000000044973c in main (argc=1, argv=0x7f7fffffdbd8) at main.c:181

So somehow mlterm ends up trying to memcpy NULL while redrawing the
cursor after I hit space.

What other tests can I run to help narrow down the root cause of the
problem?

Thanks for your help,

--
IDL

Re: [Mlterm-dev-en] mlterm 3.7.0 released

[Araki K. <ara...@us...>]

 Hi,

From: Amadeusz Sławiński <am...@as...>
Subject: Re: [Mlterm-dev-en] mlterm 3.7.0 released
Date: Wed, 16 Mar 2016 22:00:05 +0100
Message-ID: <20160316220005.2b48eb4d@medusa.ocean>

amade> so I tried building it from source, but it seems to fail for me:
amade> 
amade>  /usr/lib/gcc/x86_64-pc-linux-gnu/5.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: .libs/main.o:
amade>  undefined reference to symbol 'sqrt@@GLIBC_2.2.5' /lib64/libm.so.6:
amade>  error adding symbols: DSO missing from command line collect2: error:
amade>  ld returned 1 exit status Makefile:31: recipe for target 'registobmp'
amade>  failed make[1]: *** [registobmp] Error 1
amade> make[1]: Leaving directory '/tmp/mlterm-3.7.0/tool/registobmp'
amade> Makefile:4: recipe for target 'all' failed
amade> make: *** [all] Error 2
amade> 
amade> It seems like "-lm" was removed in this commit:
amade> https://bitbucket.org/arakiken/mlterm/commits/400952a310c1e2c612e8cf3c8318505b9347cf95#chg-tool/registobmp/Makefile.in

 Thanks.
 This is my careless mistake.
 I undid the commit.

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

Re: [Mlterm-dev-en] mlterm 3.7.0 released

[Amadeusz S. <am...@as...>]

Hey,

so I tried building it from source, but it seems to fail for me:

 /usr/lib/gcc/x86_64-pc-linux-gnu/5.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: .libs/main.o:
 undefined reference to symbol 'sqrt@@GLIBC_2.2.5' /lib64/libm.so.6:
 error adding symbols: DSO missing from command line collect2: error:
 ld returned 1 exit status Makefile:31: recipe for target 'registobmp'
 failed make[1]: *** [registobmp] Error 1
make[1]: Leaving directory '/tmp/mlterm-3.7.0/tool/registobmp'
Makefile:4: recipe for target 'all' failed
make: *** [all] Error 2

It seems like "-lm" was removed in this commit:
https://bitbucket.org/arakiken/mlterm/commits/400952a310c1e2c612e8cf3c8318505b9347cf95#chg-tool/registobmp/Makefile.in

Readding it seems to fix the issue, but it should probably be detected
at ./configure time.

Amadeusz


On Sun, 13 Mar 2016 20:00:29 +0900 (JST)
Araki Ken <ara...@us...> wrote:

>  Hi,
> 
>  This is to announce the release of mlterm version 3.7.0
> 
>  http://sourceforge.net/projects/mlterm/files/01release/mlterm-3.7.0/mlterm-3.7.0.tar.gz/download
> 
>  SHA1 (mlterm-3.7.0.tar.gz) = 10900f0303c39cdc6e5d52da6eab569b4410c777
> 
> Overview of changes from 3.6.3
> ===============================
> ver 3.7.0
> * Support OSC 1337. (See http://www.iterm2.com/images.html)
> * Support animation gif of OSC 5379 show_picture on MacOSX/cocoa.
> * Enable to place configuration files in mlterm.app/mlterm/ on
> MacOSX/Cocoa.
> * Add 'mlfc' tool which automatically generates ~/.mlterm/aafont and
> ~/.mlterm/font-fb.
> * Change the format of ~/.mlterm/*font is changed as follows.
>   [Charset] = [Font name];[Size],[Font name];[Size],[Font name];...
>   -> [Charset] = [Font name]  
> * Drop XT_CBLINK (CSI?12h/CSI?12l) support.
> * Simplify font configuration of OSC 5379. ('mlcc font USASCII <Font
> name>' is available.)
> * "CSI 38;2;r;g;b m" and "CSI 48;2;r;g;b m" shows high colors instead
> of approximate vt 256 colors. "vt_color_mode" /
> --vtcolor(=256/high/true) option changes the behavior.
> * Bug fixes:
>   Fix illegal memory access on MacOSX/Cocoa and Android.
>   Fix segfault in spliting window on MacOSX/Cocoa. (Enbugged at 3.6.2)
> 
> ---
> Araki Ken
> ara...@us...
> 
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlt...@li...
> https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en

Re: [Mlterm-dev-en] mlterm and truecolor

[Araki K. <ara...@us...>]

 Hi,

 I'm sorry to reply late.

From: Amadeusz Sławiński <am...@as...>
Subject: [Mlterm-dev-en] mlterm and truecolor
Date: Thu, 3 Sep 2015 17:04:53 +0000
Message-ID: <20150903170453.3785cc95@medusa.ocean>

> while running my truecolor test script
> (https://raw.githubusercontent.com/amade/scripts/master/misc/colors-truecolor.sh)
> in mlterm I noticed it's bit inconsitent with simulating truecolor
> color space. I attached two screenshots, one is from xterm, which also
> maps truecolor to 256 colors and other one is from mlterm.
> 
> First issue is that mlterm seems to replace some of dark blue colors
> with greys.
> 
> Other one is: out of place colors near the bottom.
> They seem to be caused by bug in my script, however, xterm seems to
> work around it (I assume by falling back to black) if there are missing
> numbers in escape sequence
> 
> Following command should probably produce black (or near black?):
> echo -e "\e[1;1H\e[48;2;6;0;0m \e[1;1H\e[48;2;6;0;m "
> however it produces dark blue, it's caused by missing color in second
> escape sequence (between ';' and 'm'). It seems that mlterm assumes
> that missing color is 0xff instead of 0x0?

 I fixed it. Thanks.

> While on topic of truecolor, are there any plans of having full
> truecolor emulation instead of mapping to 256 color space?

 Now mlterm 3.7.0 supports it.

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

[Mlterm-dev-en] mlterm 3.7.0 released

[Araki K. <ara...@us...>]

 Hi,

 This is to announce the release of mlterm version 3.7.0

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

 SHA1 (mlterm-3.7.0.tar.gz) = 10900f0303c39cdc6e5d52da6eab569b4410c777

Overview of changes from 3.6.3
===============================
ver 3.7.0
* Support OSC 1337. (See http://www.iterm2.com/images.html)
* Support animation gif of OSC 5379 show_picture on MacOSX/cocoa.
* Enable to place configuration files in mlterm.app/mlterm/ on MacOSX/Cocoa.
* Add 'mlfc' tool which automatically generates ~/.mlterm/aafont and ~/.mlterm/font-fb.
* Change the format of ~/.mlterm/*font is changed as follows.
  [Charset] = [Font name];[Size],[Font name];[Size],[Font name];...
  -> [Charset] = [Font name]
* Drop XT_CBLINK (CSI?12h/CSI?12l) support.
* Simplify font configuration of OSC 5379. ('mlcc font USASCII <Font name>' is available.)
* "CSI 38;2;r;g;b m" and "CSI 48;2;r;g;b m" shows high colors instead of
  approximate vt 256 colors. "vt_color_mode" / --vtcolor(=256/high/true) option
  changes the behavior.
* Bug fixes:
  Fix illegal memory access on MacOSX/Cocoa and Android.
  Fix segfault in spliting window on MacOSX/Cocoa. (Enbugged at 3.6.2)

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

[Mlterm-dev-en] Capital Gains & CFDs Solutions for Active US citizens Traders

[John J. <sa...@of...>]

Capital Gains & CFDs Solutions for Active US citizens Traders


Reduce your tax bills by transferring capital gains of trading stocks, bonds, options and futures into an offshore company. In other words, you will be able to exploit the Deferral Tax rules of IRS, just like US multinational companies do.

This solution applies to traders, who are
Actively trading or investing
in the capital markets and it is
100% Lawful.

You will be able to trade with in US and International markets through a single account.

What do you get:

*      An overseas company tax resident in a European Country

*      Tax free trading account

*      A corporate bank account in Europe

*      A trading account in US and UK

*      Access to CFDs

Setup Cost and -Time Required

*      Prices start from US$7569

*      Company Setup 7 days

*      Trading and Bank account opening (14 Days)

*      100% Remotely. No need for personal visit!

Documents Required

*      Notarized Passport

*      Utility Bill

*      Bank / Portfolio Statement





Exit Strategy

*      Go for holidays in outside US for 184 days in one calendar year

*      Contact us for other ways


This solution does Not apply to portfolios with investment strategies of receiving stable income in the form of Dividends, Interest, Annuities, Royalty Income and most importantly Rentals from US properties. However, the solution does apply, if Dividends and Interest income represents less than 50% of the total revenue for a calendar year. For example, a balanced portfolio with focused on capital appreciation, which also receives interest and dividends would be fine, provided that capital gains or losses from securities trading makes up at least 50% of the revenue.


Genshape Management Limited
Email: in...@of...<mailto:in...@of...>
Tel: 00357 2575 1831
Web: www.offshoreinc365.eu<http://www.offshoreinc365.eu>
Address: 17 Arch Makarios street, 2nd Floor Limassol, Cyprus



All rights reserved.

[Mlterm-dev-en] mlterm 3.6.3 released

[Araki K. <ara...@us...>]

 Hi,

 This is to announce the release of mlterm version 3.6.3

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

 SHA1 (mlterm-3.6.3.tar.gz) = b069a0bc47a5bcb4256ebb87294c9451ed25c5c6

Overview of changes from 3.6.2
===============================
ver 3.6.3
* Bug fixes:
  Fix compiling error when ./configure is executed with
  "--with-gui=fb (--disable-anti-alias)" or
  "--with-gui=xlib,fb --enable-anti-alias" option.

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

[Mlterm-dev-en] mlterm 3.6.2 released

[Araki K. <ara...@us...>]

 Hi,

 This is to announce the release of mlterm version 3.6.2

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

 SHA1 (mlterm-3.6.2.tar.gz) = 655342c3fb07590142e754152b8973347d399fdc

Overview of changes from 3.6.1
===============================
ver 3.6.2
* Support composition of normalized unicode characters on MacOSX.
* Support visual and audible bell on MacOSX/Cocoa.
* Support KAM(CSI2h, CSI2l), SRM (CSI12h, CSI12l), DECBKM(CSI?67h, CSI?67l),
  DA3(CSI=c), DECDSR(CSI?n), WYSTCURM(CSI33h, CSI33l) OSC 104 and OSC 105.
* Snapshot screen and backlog by MC(CSI i).
* Add "use_ot_layout" / --otl option which enables to show substituting glyphs
  in open type fonts with the use of libotf or harfbuzz.
  (To layout indic scripts, build mlterm with harfbuzz (not libotf), add an
  indic script font to ~/.mlterm/*font, and start mlterm with -otl option.
  See mlterm-3.6.2/doc/en/README.indic in detail.)
* Add "OpenType Layout" to "Encoding" tab of mlconfig.
* Add "ot_script" / --ost and "ot_features" / --oft.
* Add "regard_uri_as_word" / --uriword option which enables to select URI by double click
  regardless of "word_separators" option.
* Change the default value of "type_engine" option from "xft" to "cairo".
* Add vte_terminal_{set|get}_word_char_exceptions() to libvte compatible library.
* Add "Select URI by double click" to "Others" tab of mlconfig.
* Bug fixes:
  Fix "child-exited" signal of libvte (0.38 or later) compatible library.
  Fix position of a mouse pointer when EV_ABS event is received on Linux/Framebuffer.

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

[Mlterm-dev-en] Happy New Year

[Starting Business.P. <co...@st...>]

[cid:image001.jpg@01D14488.22FF6920]<http://www.offshoreinc365.eu/>

Happy Holidays
Enjoy the Season

We wish all our friends and affiliates of Genshape Management a wonderful festive season and a great start to the New Year.
In 2016, we look forward to assist with your business needs, and we wish all of you a very prosperous 2016.



Genshape Management | 2nd Floor, 17 Arch. Makarios Avenue, Limassol, PC4000, Cyprus
Phone: 00357 2575 1831 | www.startingbusiness.pro<http://www.startingbusiness.pro>

All rights reserved.

[Mlterm-dev-en] mlterm 3.6.1 released

[Araki K. <ara...@us...>]

 Hi,

 This is to announce the release of mlterm version 3.6.1

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

 SHA1 (mlterm-3.6.1.tar.gz) = 53ae7f9e41696102adc0b797b9cd28a875ae4e79

Overview of changes from 3.6.0
===============================
ver 3.6.1
* Support DECDHL and DECDWL.
* Support button event mouse tracking (CSI?1002) and any event mouse tracking (CSI?1003)
  in MacOSX/Cocoa and Android.
* Support blinking cursor in MacOSX/Cocoa.
* Add 'autohide' value to 'scrollbar_mode' option.
* Disable conversion from Unicode to ISCII if use_ctl = false.
* Drop mlterm.ti and mlterm.tc which haven't been maintained recently.
* Build 'extra' and 'pixmap_engine' scrollbars by default.
* Enable following configure options by default.
  --enable-ind, --enable-ssh2, --enable-utmp, --enable-uim, --enable-m17nlib,
  --enable-scim, --enable-ibus, --enable-fcitx, --enable-canna, --enable-wnn
* Support ssh2 connection on framebuffer.
* Set XID of text screen instead of top window as the value of WINDOWID environmental variable.
* Bug fixes:
  Fix a bug which disabled CSI?3h and CSI?3l. (Enbugged at 3.6.0)

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

[Mlterm-dev-en] mlterm 3.6.0 released

[Araki K. <ara...@us...>]

 Hi,

 This is to announce the release of mlterm version 3.6.0

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

 SHA1 (mlterm-3.6.0.tar.gz) = a71fd2643e19e96bba9b452620c6ae80bdcce4df

Overview of changes from 3.5.1
===============================
ver 3.6.0
* Support MacOSX/Cocoa. (See doc/en/README.cocoa)
* Add "geometry" to OSC 5379.
* Add "mlconfig" to OSC 5379.
* Add "Columns" and "Rows" to "Others" tab of mlconfig.
* Bug fixes:
  Fix segfault of libvte compatible library if conf_menu_path_N option is specified.

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

[Mlterm-dev-en] mlterm and truecolor

[Amadeusz S. <am...@as...>]

Hi,

while running my truecolor test script
(https://raw.githubusercontent.com/amade/scripts/master/misc/colors-truecolor.sh)
in mlterm I noticed it's bit inconsitent with simulating truecolor
color space. I attached two screenshots, one is from xterm, which also
maps truecolor to 256 colors and other one is from mlterm.

First issue is that mlterm seems to replace some of dark blue colors
with greys.

Other one is: out of place colors near the bottom.
They seem to be caused by bug in my script, however, xterm seems to
work around it (I assume by falling back to black) if there are missing
numbers in escape sequence

Following command should probably produce black (or near black?):
echo -e "\e[1;1H\e[48;2;6;0;0m \e[1;1H\e[48;2;6;0;m "
however it produces dark blue, it's caused by missing color in second
escape sequence (between ';' and 'm'). It seems that mlterm assumes
that missing color is 0xff instead of 0x0?

While on topic of truecolor, are there any plans of having full
truecolor emulation instead of mapping to 256 color space?


Amadeusz

[Mlterm-dev-en] mlterm 3.5.1 released

[Araki K. <ara...@us...>]

 Hi,

 This is to announce the release of mlterm version 3.5.1

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

 SHA1 (mlterm-3.5.1.tar.gz) = 03ce3058ae85d3e6e59ba7e9d7fe3a43cf7bf942

Overview of changes from 3.5.0
===============================
ver 3.5.1
* Support font fallback on cairo.
* Improve romaji-kana conversion in using wnn as an input method.
  (Merge https://gist.github.com/tsutsui/1d4f9af3b4a53c906eb4)
* KBD_INPUT_NUM or MOUSE_INPUT_NUM environmental variables enable to specify N
  of /dev/input/eventN on Linux/framebuffer.
* Update unicode properties to 8.0.0.
* Add "layout_inner_border" / --lborder option.
* Add "use_extended_scroll_shortcut" to OSC 5379 and 5380.
* Add "Scroll by Shift+Up or Shift+Down" to "Others" tab of mlconfig.
* Add "Font width" (Narrow/Widen/Default) entry to "Font" tab of mlconfig.
* Bug fixes:
  Change the version of libvte 2.91 compatible library from 9.0.0 to 0.0.0
  Clean up utmp entry in exiting on NetBSD.

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

Re: [Mlterm-dev-en] non-printable characters in mlterm

[B W. <ya...@gm...>]

On 8/16/15, hosein sadeqzade <h_s...@ou...> wrote:

> I found mlterm the best tool to show Persian man pages but it seems that it
> doesn't have needed ability to render non-printable characters like Zero
> Width Space and RTL/LTR markup and returns their code (see attached image).
> This is not a font issue since mlterm repeats this behavior for all fonts.

I'm pretty sure the <U200C> stuff comes from less. As a test, try:

MANPAGER=cat man explodepkg

If that looks correct, then all you have to do is find a pager that
handles the unicode characters that less isn't handling... there's a
pager called 'most' that might do a better job.

"RTL/LTR markup" means Persian is a bidirectional language, right? You
might look for a pager that lists "bidi support" as a feature.

[Mlterm-dev-en] non-printable characters in mlterm

[hosein s. <h_s...@ou...>]

Hi all

I am hosein sadeqzade and currently I am contributing to Slint project. Trying to bring Slackware installer an man pages in Persian languages.

I found mlterm the best tool to show Persian man pages but it seems that it doesn't have needed ability to render non-printable characters like Zero Width Space and RTL/LTR markup and returns their code (see attached image). This is not a font issue since mlterm repeats this behavior for all fonts.

Do you know a way to fix this issue?

I am pretty newbie in Linux so forgive me if my question is amateurish.

Best regards
Hosein
 		 	   		  

Re: [Mlterm-dev-en] Support for Pragmata Pro Ligatures

[Araki K. <ara...@us...>]

 Hi,

From: Sam Stuewe <hal...@ar...>
Subject: [Mlterm-dev-en] Support for Pragmata Pro Ligatures
Date: Sun, 9 Aug 2015 20:59:13 -0500
Message-ID: <20150810015913.GA15704@Atlas>

> It seems that mlterm already supports ligatures for various languages;
> is it possible that it will eventually support Pragmata Pro's coding
> ligatures as well?

I've never used pragmata pro, so I searched it and found this.
http://www.fsd.it/fonts/pragmatapro/PragmataPro_Haskell_liga.png

Do you want mlterm to support these ligatures ?

It isn't impossible, but it may take quite a time, sorry.

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

[Mlterm-dev-en] Support for Pragmata Pro Ligatures

[Sam S. <hal...@ar...>]

Hello all!

I'm a C/Haskell dev primarily on Linux-based platforms and I've recently
acquired a copy of Pragmata Pro. I, unlike many (I think) devs in a
similar situation, I much prefer a plain TE-based text editor over a
large IDE, but there is one feature I'm missing: ligature support for
Pragmata Pro.

To my surprise and joy, mlterm was one of the few X TEs out there that
correctly renders Pragmata Pro (note: /not/ Pragmata Pro Mono) as
monospace despite its not quite being truly monospaced. However, mlterm
still does not render the beautiful ligatures that the font's creator
has made available.

It seems that mlterm already supports ligatures for various languages;
is it possible that it will eventually support Pragmata Pro's coding
ligatures as well?

All the best,

-Sam

Re: [Mlterm-dev-en] Getting a fallback font in mlterm

[Araki K. <ara...@us...>]

From: Chris S <k...@rd...>
Subject: Re: [Mlterm-dev-en] Getting a fallback font in mlterm
Date: Sat, 20 Jun 2015 15:24:31 +0200
Message-ID: <20150620132431.25224.11815@vigilance>

> Thank you for the hint, Ken! Does this mean that I have to figure out
> the Unicode ranges for all characters not supported by my font, and
> assign a font specifically to those?
> Would it be possible to easily use my font for most Western European
> languages, and some single fallback font for everything outside that
> range? How do I go about figuring out what the interesting ranges in
> this case is?

 Now hg head at http://bitbucket.org/arakiken/mlterm supports automatic
fallback. This feature is enabled only if type_engine = cairo.

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

Re: [Mlterm-dev-en] Getting a fallback font in mlterm

[Chris S <k...@rd...>]

Quoting Araki Ken (2015-06-07 08:51:35)
>  For now, mlterm doesn't use pango to draw text on a screen, so you can't
> fall back to another font by configuring fontconfig.
>  If you want to use multiple fonts for unicode characters, configure
> ~/.mlterm/aafont manually as follows.
> 
> ISO10646_UCS4_1=Generic font
> U+0590-05FF=Hebrew font
> U+0E00-0E7F=Thai font
> ...

Thank you for the hint, Ken! Does this mean that I have to figure out
the Unicode ranges for all characters not supported by my font, and
assign a font specifically to those?

Would it be possible to easily use my font for most Western European
languages, and some single fallback font for everything outside that
range? How do I go about figuring out what the interesting ranges in
this case is?

Regards,
Chris

Re: [Mlterm-dev-en] mlterm-fb on recent Linux kernels?

[Araki K. <ara...@us...>]

 Hi,

From: B Watson <ya...@gm...>
Subject: [Mlterm-dev-en] mlterm-fb on recent Linux kernels?
Date: Wed, 3 Jun 2015 14:57:37 -0400
Message-ID: <CAN1hMuD_8=W2J...@ma...>

> Trying to build mlterm-fb (mlterm-3.4.5, ./configure --enable-gui=fb),
> on either x86 or x86_64 Slackware Linux. The x86 machine runs a 3.10.17
> kernel, the x86_64 one runs 4.0.4. I notice doc/en/README.fb talks about
> 2.6 kernels, so I wonder if it's been tested lately...
> 
> The 'make install-fb' target is broken: It tries to run sub-makes
> in inputmethods/*/ when most of those directories don't have
> Makefiles. Worked around that with:
> 
> sed -i 's,\(for dir in main inputmethod/\)\*,\1kbd/,' Makefile.in

 Thanks. I fixed it.

> Afterwards, it seems to build fine with this:
> 
>   ./configure \
>     --prefix=/usr \
>     --sysconfdir=/etc \
>     --localstatedir=/var \
>     --mandir=/usr/man \
>     --disable-static \
>     --without-x \
>     --with-gui=fb \
>     --enable-anti-alias
>   make
>   make install-fb
> 
> ...this is on a system that already has mlterm installed to /usr.
> 
> When running mlterm-fb, I get a lovely terminal display, with a shell
> prompt and a mouse pointer, but nothing I type shows up in the terminal,
> and the mouse pointer never moves.

 mlterm-fb 3.4.5 works on my Ubuntu 14.10 (kernel 3.16.0-23-generic).
 I tried steps you wrote after I received your mail, but all I type shows
up correctly and the mouse pointer moves as expected.
 I'm sorry but I have no idea to solve this problem for now.

> It's not a permission error on /dev/input/event*, since I was running
> it as root, and strace shows they're being opened without error.
> 
> When mlterm-fb is in this 'frozen' state, I can switch to another console
> and see that mlterm is still running. If I kill it... then when I switch
> back to the console where I ran mlterm-fb, all my keystrokes show up there
> (in the regular console shell that I ran mlterm-fb from).
> 
> Tried using 'openvt -s mlterm-fb' to run it on an unallocated tty (one
> that doesn't already have my shell running on it), but same results.
> 
> I don't see anything in ~/.mlterm/msg.log, and I don't see a --verbose
> or --debug option in the man page. I could attach the huge strace output
> file, if anyone thinks it'll help and has the time/patience to sift
> through it.
> 
> So I guess my questions are... is mlterm-fb known to be broken? Has
> anyone gotten it to work recently? Am I doing something obviously wrong?

 I think few people use mlterm-fb on Linux, (though some crazy
people use it on *BSD.)
 Will you send me (ara...@us...) strage output file ?

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

Re: [Mlterm-dev-en] Getting a fallback font in mlterm

[Araki K. <ara...@us...>]

 Hi,

From: Chris <k...@rd...>
Subject: [Mlterm-dev-en] Getting a fallback font in mlterm
Date: Sat, 23 May 2015 09:23:26 +0200
Message-ID: <20150523092326.5aefee53@vigilance>

k> I've been using mlterm for a while, and I've only been having one
k> problem. When my font doesn't have a character being displayed, it
k> shows as a box instead of falling back to a font that does have it.
k> 
k> I tried looking into fontconfig for this, but it appears as though
k> fontconfig does the right thing, and mlterm doesn't use fontconfig. Is
k> there a way to specify that I want to use my selected font for all
k> Unicode characters it has, and fall back to another font for the
k> characters it doesn't have?

 Pango library which many modern applications uses via toolkit libraries
such as gtk+ enables you to get a fallback font.
 For now, mlterm doesn't use pango to draw text on a screen, so you can't
fall back to another font by configuring fontconfig.
 If you want to use multiple fonts for unicode characters, configure
~/.mlterm/aafont manually as follows.

ISO10646_UCS4_1=Generic font
U+0590-05FF=Hebrew font
U+0E00-0E7F=Thai font
...

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