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

Re: [Mlterm-dev-en] 3.1.0 crash

[Andi C. S. <ski...@ya...>]

--- On Sun, 6/10/12, Araki Ken <ara...@us...> wrote:

> From: Araki Ken <ara...@us...>
> Subject: Re: [Mlterm-dev-en] 3.1.0 crash
> To: ski...@ya..., mlt...@li...
> Date: Sunday, June 10, 2012, 10:01 PM
>  Hi,
> 
>  For now I fixed following two problems.
>  Please test the attached patch(for
> mlterm-3.1.3pre-20120609.tar.gz).
> 
> From: Andi Cristian Serbanescu <ski...@ya...>
> Subject: Re: [Mlterm-dev-en] 3.1.0 crash
> Date: Sat, 9 Jun 2012 08:29:58 -0700 (PDT)
> Message-ID: <133...@we...>
> 
> > > > 1. When modifying the character cell width,
> for both
> > > xft and core fonts,
> > > > the glyph is shown at the very left of the
> cell.
> > > Shouldn't it be in the
> > > > centre? It doesn't look very nice when the
> cursor is
> > > above it.
> > > 
> > >  I fixed.
> > 
> > This one works only for core fonts.
> 
>  Do you specify the character cell width by the way like
> "DEFAULT = FONTNAME:200"
> in ~/.mlterm/font ?
>  I fixed the problem of this case.
>  (The previous fix centers characters if the character cell
> width is specified
> by "letter_space" option.)
> 

Yes, that's how I was doing it (I didn't know about letter_space). It
works now. Thanks

> > > > 3. If you don't want the option I was talking
> about
> > > some time ago
> > > > (although I hope you will change your mind in
> the
> > > future), can something
> > > > be done to disable bold characters (like
> xterm's
> > > allowBoldFonts)?
> > > 
> > >  I added "use_bold_font" option.
> > >  Start mlterm with "--bdfont=false" option or
> "use_bold_font
> > > = false" in
> > > ~/.mlterm/main, and bold fonts are disabled.
> > > 
> > 
> > This one also disables bd_color along with bold fonts
> (one may still
> > want to represent the bold attributes by means of
> colour, even if there
> > will be only one font weight).
> 
>  Oops. I Fixed.
> 

Works for me too.

>  Regards,
> ---
> Araki Ken
> ara...@us...
> 
> -----Inline Attachment Follows-----
> 
> diff -r 0d4023fb9cab
> xwindow/libtype/x_font_ft.c
> --- a/xwindow/libtype/x_font_ft.c    Sat Jun
> 09 05:10:58 2012 +0900
> +++ b/xwindow/libtype/x_font_ft.c    Mon Jun
> 11 06:50:00 2012 +0900
> @@ -603,6 +603,10 @@
>  
>      slant = -1 ;    /* use
> default value */
>  
> +    /*
> +     * x_off related to percent is
> set before ft_font_open while
> +     * x_off related to
> is_vertical and letter_space is set after.
> +     */
>      font->x_off = 0 ;
>  
>      if( fontname)
> @@ -630,16 +634,30 @@
>              {
>             
>     /* basic font (e.g. usascii) width */
>  
> +           
>     /* if font->is_var_col_width is true,
> 0 is returned. */
>             
>     ch_width = get_fc_col_width( font ,
> fontsize_d , percent ,
>             
>            
>         letter_space) ;
>  
> +           
>     if( percent > 100 &&
> use_xft)  /* cairo ignores percent. */
> +           
>     {
> +           
>         /*
> +           
>          *
> Centering
> +           
>          * (fontsize
> * percent / 100 + letter_space = ch_width
> +           
>          * 
> -> fontsize = (ch_width - letter_space) * 100 / percent
> +           
>          * 
> -> fontsize * (percent - 100) / 100
> +           
>          * 
>    = (ch_width - letter_space) * (percent -
> 100)
> +           
>          * 
>      / percent)
> +           
>          */
> +           
>         font->x_off =
> (ch_width - letter_space) *
> +           
>            
>     (percent - 100) / percent / 2 ;
> +           
>     }
> +
>             
>     if( font->is_vertical)
>             
>     {
>             
>         /*
>             
>          * !! Notice
> !!
>             
>          * The width
> of full and half character font is the same.
>             
>          */
> -           
>         font->x_off =
> ch_width / 2 ;
>             
>         ch_width *= 2 ;
>             
>     }
>              }
> @@ -677,6 +695,8 @@
>              {
>             
>     goto  font_found ;
>              }
> +
> +           
> font->x_off = 0 ;
>          }
>  
>          kik_msg_printf( "Font
> %s (for size %f) couldn't be loaded.\n" ,
> @@ -695,7 +715,6 @@
>         
>      * !! Notice !!
>         
>      * The width of full and half
> character font is the same.
>         
>      */
> -           
> font->x_off = ch_width / 2 ;
>             
> ch_width *= 2 ;
>          }
>      }
> @@ -770,12 +789,15 @@
>          else
>          {
>             
> font->width = ch_width ;
> -        }
>  
> -        /* letter_space is
> ignored in variable column width mode. */
> -        if( !
> font->is_var_col_width)
> -        {
> -           
> font->x_off += letter_space * font->cols / 2 ;
> +           
> if( font->is_vertical && font->cols == 1)
> +            {
> +           
>     font->x_off += ch_width / 4
> ;    /* Centering */
> +            }
> +           
> else
> +            {
> +           
>     font->x_off += letter_space *
> font->cols / 2 ;
> +            }
>          }
>  
>      #endif    /* USE_TYPE_XFT
> */
> @@ -820,6 +842,7 @@
>              {
>             
>     font->is_proportional = 1 ;
>             
>     font->width *= 2 ;
> +           
>     font->x_off = font->width / 4
> ;    /* Centering */
>              }
>          }
>  
> @@ -828,7 +851,7 @@
>          {
>             
> font->is_proportional = 1 ;
>             
> font->width += (letter_space * font->cols) ;
> -           
> font->x_off += (letter_space * font->cols / 2) ;
> +           
> font->x_off += (letter_space * font->cols / 2) ; 
> /* Centering */
>          }
>  
>          if( col_width > 0
> /* is not usascii */ && ! font->is_proportional
> &&
> diff -r 0d4023fb9cab xwindow/x_draw_str.c
> --- a/xwindow/x_draw_str.c    Sat Jun 09
> 05:10:58 2012 +0900
> +++ b/xwindow/x_draw_str.c    Mon Jun 11
> 06:50:00 2012 +0900
> @@ -16,11 +16,11 @@
>      x_color_manager_t *  color_man ,
>      ml_color_t  fg_color ,
>      ml_color_t  bg_color ,
> -    ml_font_t  font ,
> +    int  is_bold ,
>      int  is_underlined
>      )
>  {
> -    if( font & FONT_BOLD)
> +    if( is_bold)
>      {
>          /* If bg_color ==
> ML_FG_COLOR, it seems to be reversed. */
>          if( ( fg_color ==
> ML_FG_COLOR || bg_color == ML_FG_COLOR) &&
> @@ -139,6 +139,7 @@
>      u_int  ch_width ;
>      mkf_charset_t  ch_cs ;
>      x_font_t *  xfont ;
> +    ml_font_t  font ;
>      ml_color_t  fg_color ;
>      ml_color_t  bg_color ;
>      int  is_underlined ;
> @@ -146,6 +147,7 @@
>      u_int  comb_size ;
>  
>      x_font_t *  next_xfont ;
> +    ml_font_t  next_font ;
>      ml_color_t  next_fg_color ;
>      ml_color_t  next_bg_color ;
>      int  next_is_underlined ;
> @@ -178,7 +180,8 @@
>  
>      ch_bytes = ml_char_bytes(
> &chars[count]) ;
>      ch_size = ml_char_size(
> &chars[count]) ;
> -    ch_cs = ml_char_cs( &chars[count])
> ;
> +    xfont = x_get_font( font_man , (font =
> ml_char_font( &chars[count]))) ;
> +    ch_cs = FONT_CS(font) ;
>  
>      if( ch_cs == US_ASCII || ch_cs ==
> ISO8859_1_R || IS_ISCII(ch_cs))
>      {
> @@ -193,8 +196,6 @@
>          state = 2 ;
>      }
>  
> -    xfont = x_get_font( font_man ,
> ml_char_font( &chars[count])) ;
> -
>      ch_width = x_calculate_char_width( xfont
> , ch_bytes , ch_size , ch_cs) ;
>  
>      if( ( current_width = x + ch_width) >
> window->width ||
> @@ -228,11 +229,7 @@
>  
>      while( 1)
>      {
> -        if( state == 0)
> -        {
> -           
> str8[str_len++] = ch_bytes[0] ;
> -        }
> -        else if( state == 1)
> +        if( state == 0 ||
> state == 1)
>          {
>             
> str8[str_len++] = ch_bytes[0] ;
>          }
> @@ -277,11 +274,12 @@
>          {
>             
> ch_bytes = ml_char_bytes( &chars[count]) ;
>             
> ch_size = ml_char_size( &chars[count]) ;
> -           
> ch_cs = ml_char_cs( &chars[count]) ;
> +           
> next_xfont = x_get_font( font_man ,
> +           
>         (next_font =
> ml_char_font( &chars[count]))) ;
> +           
> ch_cs = FONT_CS(next_font) ;
>             
> next_fg_color = ml_char_fg_color( &chars[count]) ;
>             
> next_bg_color = ml_char_bg_color( &chars[count]) ;
>             
> next_is_underlined = ml_char_is_underlined(
> &chars[count]) ;
> -           
> next_xfont = x_get_font( font_man , ml_char_font(
> &chars[count])) ;
>  
>             
> if( ch_cs == US_ASCII || ch_cs == ISO8859_1_R ||
> IS_ISCII(ch_cs))
>              {
> @@ -307,19 +305,26 @@
>             
> /*
>         
>      * !! Notice !!
>         
>      * next_xfont != xfont doesn't
> necessarily detect change of 'state'
> -       
>      * (for example, same Unicode
> font is used for both US_ASCII/ISO8859_1
> -       
>      * and other half-width unicode
> characters), 'next_state' is necessary.
> +       
>      * (for example, same Unicode
> font is used for both US_ASCII and
> +       
>      * other half-width unicode
> characters) and 'bold'(x_get_font()
> +       
>      * might substitute normal
> fonts for bold ones), 'next_state' and
> +       
>      * 'font & FONT_BOLD' is
> necessary.
>         
>      */
>             
> else if( next_xfont != xfont
>             
>     || next_fg_color != fg_color
>             
>     || next_bg_color != bg_color
>             
>     || next_is_underlined != is_underlined
> +           
>     /*
> +           
>      * Eevn if both is_underline
> and next_is_underline are 1,
> +           
>      * underline is drawn one by
> one in vertical mode.
> +           
>      */
>             
>     || (is_underlined &&
> xfont->is_vertical)
> -           
>     || (next_is_underlined &&
> xfont->is_vertical)
>             
>     || comb_chars != NULL
>             
>     || state != next_state
>             
>     || (next_xfont->is_proportional
> && ! next_xfont->is_var_col_width)
> -           
>     || (xfont->is_proportional &&
> ! xfont->is_var_col_width))
> +           
>     || (xfont->is_proportional &&
> ! xfont->is_var_col_width)
> +           
>     /* FONT_BOLD flag is not the same. */
> +           
>         || ((font ^ next_font) &
> FONT_BOLD))
>              {
>             
>     start_draw = 1 ;
>              }
> @@ -342,7 +347,7 @@
>          #endif
>  
>             
> color_adjusted = adjust_bd_ul_color( color_man , fg_color ,
> bg_color ,
> -           
>            
>     xfont->id , is_underlined) ;
> +           
>            
>     font & FONT_BOLD , is_underlined) ;
>  
>             
> /*
>         
>      * clearing background
> @@ -444,6 +449,7 @@
>  
>          is_underlined =
> next_is_underlined ;
>          xfont = next_xfont ;
> +        font = next_font ;
>          fg_color =
> next_fg_color ;
>          bg_color =
> next_bg_color ;
>          state = next_state ;
> @@ -578,12 +584,14 @@
>      mkf_charset_t  ch_cs ;
>      u_int  ch_width ;
>      x_font_t *  xfont ;
> +    ml_font_t  font ;
>      ml_color_t  fg_color ;
>      ml_color_t  bg_color ;
>      int  is_underlined ;
>  
>      u_int  next_ch_width ;
>      x_font_t *  next_xfont ;
> +    ml_font_t  next_font ;
>      ml_color_t  next_fg_color ;
>      ml_color_t  next_bg_color ;
>      int  next_is_underlined ;
> @@ -617,7 +625,7 @@
>      ch_size = ml_char_size(
> &chars[count]) ;
>      ch_cs = ml_char_cs( &chars[count])
> ;
>  
> -    xfont = x_get_font( font_man ,
> ml_char_font( &chars[count])) ;
> +    xfont = x_get_font( font_man , (font =
> ml_char_font( &chars[count]))) ;
>  
>      ch_width = x_calculate_char_width( xfont
> , ch_bytes , ch_size , ch_cs) ;
>  
> @@ -727,7 +735,8 @@
>             
> next_fg_color = ml_char_fg_color( &chars[count]) ;
>             
> next_bg_color = ml_char_bg_color( &chars[count]) ;
>             
> next_is_underlined = ml_char_is_underlined(
> &chars[count]) ;
> -           
> next_xfont = x_get_font( font_man ,  ml_char_font(
> &chars[count])) ;
> +           
> next_xfont = x_get_font( font_man ,
> +           
>         (next_font =
> ml_char_font( &chars[count]))) ;
>  
>             
> if( ch_cs == DEC_SPECIAL)
>              {
> @@ -753,19 +762,26 @@
>             
> /*
>         
>      * !! Notice !!
>         
>      * next_xfont != xfont doesn't
> necessarily detect change of 'state'
> -       
>      * (for example, same Unicode
> font is used for both US_ASCII/ISO8859_1
> -       
>      * and other half-width unicode
> characters), 'next_state' is necessary.
> +       
>      * (for example, same Unicode
> font is used for both US_ASCII and
> +       
>      * other half-width unicode
> characters) and 'bold'(x_get_font()
> +       
>      * might substitute normal
> fonts for bold ones), 'next_state' and
> +       
>      * 'font & FONT_BOLD' is
> necessary.
>         
>      */
>             
> else if( next_xfont != xfont
>             
>     || next_fg_color != fg_color
>             
>     || next_bg_color != bg_color
>             
>     || next_is_underlined != is_underlined
> +           
>     /*
> +           
>      * Eevn if both is_underline
> and next_is_underline are 1,
> +           
>      * underline is drawn one by
> one in vertical mode.
> +           
>      */
>             
>     || (is_underlined &&
> xfont->is_vertical)
> -           
>     || (next_is_underlined &&
> xfont->is_vertical)
>             
>     || next_state != state
>             
>     || comb_chars != NULL
>             
>     || (next_xfont->is_proportional
> && ! next_xfont->is_var_col_width)
> -           
>     || (xfont->is_proportional &&
> ! xfont->is_var_col_width))
> +           
>     || (xfont->is_proportional &&
> ! xfont->is_var_col_width)
> +           
>     /* FONT_BOLD flag is not the same */
> +           
>         || ((font ^ next_font) &
> FONT_BOLD))
>              {
>             
>     start_draw = 1 ;
>              }
> @@ -788,7 +804,7 @@
>          #endif
>  
>             
> color_adjusted = adjust_bd_ul_color( color_man , fg_color ,
> bg_color ,
> -           
>            
>     xfont->id , is_underlined) ;
> +           
>            
>     font & FONT_BOLD , is_underlined) ;
>  
>             
> if( ( x_window_has_wall_picture( window) && bg_color
> == ML_BG_COLOR) ||
>             
>     bottom_margin + top_margin > 0 /* ==
> line space XXX */|| 
> @@ -916,6 +932,7 @@
>          }
>  
>          xfont = next_xfont ;
> +        font = next_font ;
>          fg_color =
> next_fg_color ;
>          bg_color =
> next_bg_color ;
>          is_underlined =
> next_is_underlined ;
> diff -r 0d4023fb9cab xwindow/x_font_config.c
> --- a/xwindow/x_font_config.c    Sat Jun 09
> 05:10:58 2012 +0900
> +++ b/xwindow/x_font_config.c    Mon Jun 11
> 06:50:00 2012 +0900
> @@ -1731,7 +1731,6 @@
>      char *  font_name ;
>      char *  encoding_name ;
>      int  has_percentd ;
> -    size_t  len ;
>      
>      if( font_size < min_font_size ||
> max_font_size < font_size)
>      {
> @@ -1756,7 +1755,9 @@
>          }
>  
>      #ifndef  USE_WIN32GUI
> -        if(
> font_config->type_engine == TYPE_XCORE)
> +        if(
> font_config->type_engine == TYPE_XCORE &&
> +            /*
> encoding_name is appended if font_name is XLFD (not alias
> name). */
> +            (
> strchr( pair->value , '*') || strchr( pair->value ,
> '-')))
>          {
>             
> char **  names ;
>  
> @@ -1789,13 +1790,11 @@
>          has_percentd = 0 ;
>      }
>  
> -    len = strlen( pair->value) +
> -        /* -2 is for "%d" */
> -        (has_percentd ?
> DIGIT_STR_LEN(font_size) - 2 : 0) +
> -        /* + 1  is for
> "-" */
> -        (encoding_name ?
> strlen(encoding_name) + 1 : 0) + 1 ;
> -
> -    if( ( font_name = malloc( len)) ==
> NULL)
> +    if( ! ( font_name = malloc( strlen(
> pair->value) +
> +           
>     /* -2 is for "%d" */
> +           
>     (has_percentd ? DIGIT_STR_LEN(font_size)
> - 2 : 0) +
> +           
>     /* + 1  is for "-" */
> +           
>     (encoding_name ? strlen(encoding_name) +
> 1 : 0) + 1)))
>      {
>          return  NULL ;
>      }
> @@ -1811,7 +1810,22 @@
>  
>      if( encoding_name)
>      {
> -        strcat( font_name ,
> encoding_name) ;
> +        char *  percent
> ;
> +
> +        if( ( percent =
> strchr( font_name , ':')))
> +        {
> +            /*
> -*-:200 -> -*-iso8859-1:200 */
> +
> +           
> size_t  len ;
> +
> +           
> memmove( percent + (len = strlen(encoding_name)) , percent
> ,
> +           
>     strlen( percent) + 1) ;
> +           
> memcpy( percent , encoding_name , len) ;
> +        }
> +        else
> +        {
> +           
> strcat( font_name , encoding_name) ;
> +        }
>      }
>  
>      return  font_name ;
> diff -r 0d4023fb9cab xwindow/xlib/x_font.c
> --- a/xwindow/xlib/x_font.c    Sat Jun 09
> 05:10:58 2012 +0900
> +++ b/xwindow/xlib/x_font.c    Mon Jun 11
> 06:50:00 2012 +0900
> @@ -477,8 +477,9 @@
>  
>          if( parse_xfont_name(
> &font_xlfd , &percent_str , p))
>          {
> -        #ifdef __DEBUG
> -           
> kik_debug_printf( KIK_DEBUG_TAG " loading %s font.\n" ,
> font_xlfd) ;
> +        #ifdef  __DEBUG
> +           
> kik_debug_printf( KIK_DEBUG_TAG " loading %s font (%s
> percent).\n" ,
> +           
>     font_xlfd , percent_str) ;
>          #endif
>  
>             
> if( ( xfont = XLoadQueryFont( font->display ,
> font_xlfd)))
> @@ -770,6 +771,10 @@
>  
>             
> if( font->width != col_width)
>              {
> +           
>     kik_msg_printf( "Font(id %x) width(%d) is
> not matched with "
> +           
>         "standard
> width(%d).\n" ,
> +           
>         font->id ,
> font->width , col_width) ;
> +
>             
>     font->is_proportional = 1 ;
>  
>             
>     /* is_var_col_width is always false if
> is_vertical is true. */
> 

Re: [Mlterm-dev-en] 3.1.0 crash

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

 Hi,

 For now I fixed following two problems.
 Please test the attached patch(for mlterm-3.1.3pre-20120609.tar.gz).

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: Re: [Mlterm-dev-en] 3.1.0 crash
Date: Sat, 9 Jun 2012 08:29:58 -0700 (PDT)
Message-ID: <133...@we...>

> > > 1. When modifying the character cell width, for both
> > xft and core fonts,
> > > the glyph is shown at the very left of the cell.
> > Shouldn't it be in the
> > > centre? It doesn't look very nice when the cursor is
> > above it.
> > 
> >  I fixed.
> 
> This one works only for core fonts.

 Do you specify the character cell width by the way like "DEFAULT = FONTNAME:200"
in ~/.mlterm/font ?
 I fixed the problem of this case.
 (The previous fix centers characters if the character cell width is specified
by "letter_space" option.)

> > > 3. If you don't want the option I was talking about
> > some time ago
> > > (although I hope you will change your mind in the
> > future), can something
> > > be done to disable bold characters (like xterm's
> > allowBoldFonts)?
> > 
> >  I added "use_bold_font" option.
> >  Start mlterm with "--bdfont=false" option or "use_bold_font
> > = false" in
> > ~/.mlterm/main, and bold fonts are disabled.
> > 
> 
> This one also disables bd_color along with bold fonts (one may still
> want to represent the bold attributes by means of colour, even if there
> will be only one font weight).

 Oops. I Fixed.

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

Re: [Mlterm-dev-en] 3.1.0 crash

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

 Hi,

 Thanks for your report.
 I fixed these problems and uploaded a fixed version.

 => http://mlterm.sf.net/mlterm-3.1.3pre-20120609.tar.gz

 Please test it.

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: Re: [Mlterm-dev-en] 3.1.0 crash
Date: Sat, 2 Jun 2012 06:45:39 -0700 (PDT)
Message-ID: <133...@we...>

> 1. When modifying the character cell width, for both xft and core fonts,
> the glyph is shown at the very left of the cell. Shouldn't it be in the
> centre? It doesn't look very nice when the cursor is above it.

 I fixed.

> 2. An option for solid and/or non-blinking (or disabled) unfocused
> cursor.

 Non-blinking when unfocused like xterm.

> 3. If you don't want the option I was talking about some time ago
> (although I hope you will change your mind in the future), can something
> be done to disable bold characters (like xterm's allowBoldFonts)?

 I added "use_bold_font" option.
 Start mlterm with "--bdfont=false" option or "use_bold_font = false" in
~/.mlterm/main, and bold fonts are disabled.

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

Re: [Mlterm-dev-en] 3.1.0 crash

[Andi C. S. <ski...@ya...>]

Hello,

Thanks for the update. I know this thread is getting old, but I still
have a few ideas.

1. When modifying the character cell width, for both xft and core fonts,
the glyph is shown at the very left of the cell. Shouldn't it be in the
centre? It doesn't look very nice when the cursor is above it.

2. An option for solid and/or non-blinking (or disabled) unfocused
cursor.

3. If you don't want the option I was talking about some time ago
(although I hope you will change your mind in the future), can something
be done to disable bold characters (like xterm's allowBoldFonts)?

Regards,
Andi Șerbănescu

[Mlterm-dev-en] mlterm 3.1.2 released

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

 Hi,

 This is to announce the release of mlterm version 3.1.2

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

MD5 (mlterm-3.1.2.tar.gz) = cdbd90b285dae9ae7216f07492e505ed
SHA1 (mlterm-3.1.2.tar.gz) = 9053475c5096a8edc74c537d675ade83066c2d90

Overview of changes from 3.1.1
===============================

ver 3.1.2
* Support extended mouse tracking mode.
  (CSI ? 1006 h and CSI ? 1006 l / CSI ? 1015 h and CSI ? 1015 l)
* Support sixel graphics sequence partially. (DCS .. q .. ST)
  (configure with --enable-sixel option.)
* Support FocusIn/FocusOut event tracking. (CSI ? 1004 h and CSI ? 1004 l)
* Support inputmethod/kbd in win32.
* Add "add_picture", "remove_picture" and "close_pty" commands to
  configuration protocol.
* Add "hide_underline" option.
* Merge SF patches:
  #3524577 (Thanks to Ahmed El-Mahmoudy)
  #3524578 (Install mlterm tools to $(libexecdir)/mlterm instead of $(libexecdir))
  (Thanks to Ahmed El-Mahmoudy)
  patch-ae in NetBSD pkgsrc x11/mlterm.
* Bug fixes:
  Fix a bug which disabled "bd_color" and "ul_color" options in reverse characters.
  (Thanks to Andi Cristian Serbanescu)
  Fix an ibus bug which causes segmentation fault if ibus daemon is not found.
  Fix a bug which could cause failure of opening a new window over ssh connection.
  Fix a bug which causes infinite loop if large OSC sequence is received.
  (Thanks to Koie Hidetaka san)
  Fix a bug which disabled mlconfig and mlterm-menu etc to start if multiple screens opened.
--
Araki Ken
ara...@us...

Re: [Mlterm-dev-en] 3.1.0 crash

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

 Hi,

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: Re: [Mlterm-dev-en] 3.1.0 crash
Date: Sun, 13 May 2012 02:59:14 -0700 (PDT)
Message-ID: <133...@we...>

> > > > RV + anything else is black on white (plus the
> > other
> > > > attributes), just as if bd_color and ul_color were
> > not
> > > > defined (although they behave as expected when
> > selected with
> > > > the mouse).
> > > > 
> > > >  Thanks. This is a bug.
> > > >  An attached patch will fix this problem.
> > > > 
> > > 
> > > I applied the patch, but it doesn't work :(
> > 
> >  I modified a little more.
> > 
> 
> I've tried it. Strangely, it works with core fonts, but not with xft. Perhaps the previous one had just the same problem, but it didn't occur to me to test it as thoroughly (I normally use xft).

 Oh, that's my careless mistake, sorry.
 An attached patch fixes this problem.

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

Re: [Mlterm-dev-en] 3.1.0 crash

[Andi C. S. <ski...@ya...>]

Hello,

--- On Sat, 5/12/12, Araki Ken <ara...@us...> wrote:

> From: Araki Ken <ara...@us...>
> Subject: Re: [Mlterm-dev-en] 3.1.0 crash
> To: mlt...@li..., ski...@ya...
> Date: Saturday, May 12, 2012, 9:20 PM
>  Hi,
> 
> From: Andi Cristian Serbanescu <ski...@ya...>
> Subject: Re: [Mlterm-dev-en] 3.1.0 crash
> Date: Thu, 10 May 2012 14:45:42 -0700 (PDT)
> Message-ID: <133...@we...>
> 
> > You are right. Xterm disables the underline for plain
> UL only (urxvt doesn't disable it at all). But xterm also
> has resources to completely disable drawing underlines and
> bold text (underLine and allowBoldFonts).
> > Initially, I had something else in mind for bold text,
> but maybe this can still be done as an extra option: if
> bd_color is not set, it would see if fg_color and ul_color
> are aliased to one of the default dim colours (0-7) and, if
> so, would handle them as if they were ordinary (ANSI)
> coloured text (i.e. highlight them if BD and apply RV before
> BD (if BD + RV), so that on the screen you would see bright
> (8-15) text on a dim (0-7) background). What do you think
> about this?
> 
>  It seems a good hack, but a little hard to understand for
> users.
> 

So I understand it's not going to be done. Too bad, because some console programs are designed with the expectation that the background will remain ‘dim’ after RV, since that's the way the console does it. It would also be consistent with the other colours and solve the ambiguity in some BD + UL cases.

I think it could explained as emulate console highlight behaviour (highlight all BD text and highlight after RV).

>  Instead I added --noul / "hide_underline" option which
> completely disables
> underline like xterm as an experiment.
> 

The option works well for me.

> > > RV + anything else is black on white (plus the
> other
> > > attributes), just as if bd_color and ul_color were
> not
> > > defined (although they behave as expected when
> selected with
> > > the mouse).
> > > 
> > >  Thanks. This is a bug.
> > >  An attached patch will fix this problem.
> > > 
> > 
> > I applied the patch, but it doesn't work :(
> 
>  I modified a little more.
> 

I've tried it. Strangely, it works with core fonts, but not with xft. Perhaps the previous one had just the same problem, but it didn't occur to me to test it as thoroughly (I normally use xft).

>  I placed a modified source tar ball at http://mlterm.sf.net/mlterm-3.1.2-pre20120512.tar.gz

Thanks for the update.

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

Regards,
Andi Șerbănescu

Re: [Mlterm-dev-en] 3.1.0 crash

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

 Hi,

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: Re: [Mlterm-dev-en] 3.1.0 crash
Date: Thu, 10 May 2012 14:45:42 -0700 (PDT)
Message-ID: <133...@we...>

> You are right. Xterm disables the underline for plain UL only (urxvt doesn't disable it at all). But xterm also has resources to completely disable drawing underlines and bold text (underLine and allowBoldFonts).
> Initially, I had something else in mind for bold text, but maybe this can still be done as an extra option: if bd_color is not set, it would see if fg_color and ul_color are aliased to one of the default dim colours (0-7) and, if so, would handle them as if they were ordinary (ANSI) coloured text (i.e. highlight them if BD and apply RV before BD (if BD + RV), so that on the screen you would see bright (8-15) text on a dim (0-7) background). What do you think about this?

 It seems a good hack, but a little hard to understand for users.

 Instead I added --noul / "hide_underline" option which completely disables
underline like xterm as an experiment.

> > RV + anything else is black on white (plus the other
> > attributes), just as if bd_color and ul_color were not
> > defined (although they behave as expected when selected with
> > the mouse).
> > 
> >  Thanks. This is a bug.
> >  An attached patch will fix this problem.
> > 
> 
> I applied the patch, but it doesn't work :(

 I modified a little more.

 I placed a modified source tar ball at http://mlterm.sf.net/mlterm-3.1.2-pre20120512.tar.gz

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

Re: [Mlterm-dev-en] 3.1.0 crash

[Andi C. S. <ski...@ya...>]

Hello,

--- On Wed, 5/2/12, Araki Ken <ara...@us...> wrote:

> From: Araki Ken <ara...@us...>
> Subject: Re: [Mlterm-dev-en] 3.1.0 crash
> To: ski...@ya..., mlt...@li...
> Date: Wednesday, May 2, 2012, 4:49 PM
>  Hi,
> 
>  Thanks for your report.
> 
> From: Andi Cristian Serbanescu <ski...@ya...>
> Subject: Re: [Mlterm-dev-en] 3.1.0 crash
> Date: Sat, 28 Apr 2012 14:15:33 -0700 (PDT)
> Message-ID: <133...@we...>
> 
> > To illustrate (having set bg_color = black, fg_color =
> white, bd_color = hl_white and ul_color = cyan), BD and UL
> appear as expected, but BD + UL is underlined hl_white on
> black (i.e. ul_color/disable underline has no effect)
> 
>  Ummm... I think xterm (and urxvt) has the same behavior.
>  Mlterm should work the same way as xterm as much as
> possible.
> 

You are right. Xterm disables the underline for plain UL only (urxvt doesn't disable it at all). But xterm also has resources to completely disable drawing underlines and bold text (underLine and allowBoldFonts).

Initially, I had something else in mind for bold text, but maybe this can still be done as an extra option: if bd_color is not set, it would see if fg_color and ul_color are aliased to one of the default dim colours (0-7) and, if so, would handle them as if they were ordinary (ANSI) coloured text (i.e. highlight them if BD and apply RV before BD (if BD + RV), so that on the screen you would see bright (8-15) text on a dim (0-7) background). What do you think about this?

> > RV + anything else is black on white (plus the other
> attributes), just as if bd_color and ul_color were not
> defined (although they behave as expected when selected with
> the mouse).
> 
>  Thanks. This is a bug.
>  An attached patch will fix this problem.
> 

I applied the patch, but it doesn't work :(

>  Regards,
> --- 
> Araki Ken
> ara...@us...
> 
> -----Inline Attachment Follows-----
> 
> diff -r 6140560880da
> mlterm/ml_color.h
> --- a/mlterm/ml_color.h    Mon Apr 30
> 20:55:14 2012 +0900
> +++ b/mlterm/ml_color.h    Thu May 03
> 01:43:20 2012 +0900
> @@ -16,6 +16,7 @@
>  #define  IS_256_COLOR(color)  (0x10 <= (color)
> && (color) <= 0xff)
>  #define  IS_VALID_COLOR_EXCEPT_FG_BG(color) 
> ((unsigned int)(color) < 0xff)
>  #define  IS_VALID_COLOR(color)  (0x0 <=
> (color) && (color) < 0x100)
> +#define  IS_FG_BG_COLOR(color)  ((color) >=
> 0x100)
>  
>  
>  typedef enum  ml_color
> diff -r 6140560880da xwindow/x_draw_str.c
> --- a/xwindow/x_draw_str.c    Mon Apr 30
> 20:55:14 2012 +0900
> +++ b/xwindow/x_draw_str.c    Thu May 03
> 01:43:20 2012 +0900
> @@ -21,7 +21,7 @@
>  {
>      if( font & FONT_BOLD)
>      {
> -        if( fg_color ==
> ML_FG_COLOR && x_color_manager_adjust_bd_color(
> color_man))
> +        if(
> IS_FG_BG_COLOR(fg_color) &&
> x_color_manager_adjust_bd_color( color_man))
>          {
>             
> return  1 ;
>          }
> @@ -29,7 +29,7 @@
>  
>      if( is_underlined)
>      {
> -        if( fg_color ==
> ML_FG_COLOR && x_color_manager_adjust_ul_color(
> color_man))
> +        if(
> IS_FG_BG_COLOR(fg_color) &&
> x_color_manager_adjust_ul_color( color_man))
>          {
>             
> return  2 ;
>          }
>

Regards,
Andi Șerbănescu

Re: [Mlterm-dev-en] Difficulty changing the font in mlterm [solved]

[John M. <lis...@b7...>]

Hi,

* Araki Ken <ara...@us...> [120509 19:16]:
> > I'm having trouble changing the font in mlterm. My goal is to display
> > UTF-8 files using Gentium, a variable width font.
> > 
> > After starting mlterm with `mlterm -A -V`, I brought up the mlterm
> > configuration panel, selected "Gentium 24" from the pull-down menu,
> > and checked the "Variable column width" option. I do see a line has
> > been added to ~./mlterm/vaafont
> > 
> >     DEFAULT = 24,Gentium 24
> > 
> > But mlterm does not display the Gentium font...it just keeps displaying
> > the same monospace font (looks like DejaVu Sans Mono) no matter what
> > font is selected.
> 
>  Will you show me your ~/.mlterm/main, ~/.mlterm/aafont and
>  ~/.mlterm/vaafont? I'm sorry but procedure of font setting is somewhat
>  complicated. Variable width unicode font is searched as follows.

All these are mostly as copied from /etc: `cp /etc/mlterm/* ~/.mlterm/`
(with the addition of the font callout for Gentium).

>  If you specify ~/.mlterm/main and ~/.mlterm/vaafont as follows
> or remove ~/.mlterm/aafont, I think you can certainly display Gentium font.
> 
> ~/.mlterm/main
> fontsize = 24
> 
> ~/.mlterm/vaafont
> DEFAULT = 24,Gentium 24
> ISO10646_UCS4_1 = 24,Gentium 24

Yes, this did it. It was necessary to specify fontsize in
~/.mlterm/main as well as those two lines in ~/.mlterm/vaafont
(I was missing the "ISO10646_UCS4_1 = 24,Gentium 24" line).
Now Gentium displays properly as a variable width font when
started with `mlterm -A`

Thanks for your help,

John

-- 
John Magolske
http://B79.net/contact

Re: [Mlterm-dev-en] Difficulty changing the font in mlterm

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

 Hi,

From: John Magolske <lis...@b7...>
Subject: [Mlterm-dev-en] Difficulty changing the font in mlterm
Date: Tue, 8 May 2012 23:20:08 -0700
Message-ID: <201...@s7...>

> I'm having trouble changing the font in mlterm. My goal is to display
> UTF-8 files using Gentium, a variable width font.
> 
> After starting mlterm with `mlterm -A -V`, I brought up the mlterm
> configuration panel, selected "Gentium 24" from the pull-down menu,
> and checked the "Variable column width" option. I do see a line has
> been added to ~./mlterm/vaafont
> 
>     DEFAULT = 24,Gentium 24
> 
> But mlterm does not display the Gentium font...it just keeps displaying
> the same monospace font (looks like DejaVu Sans Mono) no matter what
> font is selected.

 Will you show me your ~/.mlterm/main, ~/.mlterm/aafont and ~/.mlterm/vaafont?
 I'm sorry but procedure of font setting is somewhat complicated.
 Variable width unicode font is searched as follows.

1) ISO10646_UCS4_1 in vaafont
2) ISO10646_UCS4_1 in aafont
3) DEFAULT in vaafont
4) DEFAULT in aafont
 
 If you specify ~/.mlterm/main and ~/.mlterm/vaafont as follows
or remove ~/.mlterm/aafont, I think you can certainly display Gentium font.

~/.mlterm/main
fontsize = 24

~/.mlterm/vaafont
DEFAULT = 24,Gentium 24
ISO10646_UCS4_1 = 24,Gentium 24

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

[Mlterm-dev-en] Difficulty changing the font in mlterm

[John M. <lis...@b7...>]

Hi,

I'm having trouble changing the font in mlterm. My goal is to display
UTF-8 files using Gentium, a variable width font.

After starting mlterm with `mlterm -A -V`, I brought up the mlterm
configuration panel, selected "Gentium 24" from the pull-down menu,
and checked the "Variable column width" option. I do see a line has
been added to ~./mlterm/vaafont

    DEFAULT = 24,Gentium 24

But mlterm does not display the Gentium font...it just keeps displaying
the same monospace font (looks like DejaVu Sans Mono) no matter what
font is selected.

This is mlterm version 3.1.1 on Debian Linux.

Thanks for any suggestions,

John

-- 
John Magolske
http://B79.net/contact

Re: [Mlterm-dev-en] 3.1.0 crash

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

 Hi,

 Thanks for your report.

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: Re: [Mlterm-dev-en] 3.1.0 crash
Date: Sat, 28 Apr 2012 14:15:33 -0700 (PDT)
Message-ID: <133...@we...>

> To illustrate (having set bg_color = black, fg_color = white, bd_color = hl_white and ul_color = cyan), BD and UL appear as expected, but BD + UL is underlined hl_white on black (i.e. ul_color/disable underline has no effect)

 Ummm... I think xterm (and urxvt) has the same behavior.
 Mlterm should work the same way as xterm as much as possible.

> RV + anything else is black on white (plus the other attributes), just as if bd_color and ul_color were not defined (although they behave as expected when selected with the mouse).

 Thanks. This is a bug.
 An attached patch will fix this problem.

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

Re: [Mlterm-dev-en] mlterm with Devanagari

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

 Hi,

From: Mayuresh <may...@ac...>
Subject: Re: [Mlterm-dev-en] mlterm with Devanagari
Date: Sun, 22 Apr 2012 08:48:49 +0530
Message-ID: <201...@SD...>

> On Mon, Apr 02, 2012 at 09:46:29PM +0900, Araki Ken wrote:
> > > Here are mine, though not exactly matching, the ones you mentioned
> > > specifically are there:
> > 
> >  I think necessary modules are correctly installed.
> 
> For sake of a try, I upgraded to 3.1.0, though Devanagari continues to not
> work on my terminal.
> 
> Does my OS matter? It is NetBSD 6.0 BETA.

 I'm sorry but I have no idea.

 To make sure, please try following steps. (Don't use pkgsrc)

 $ tar xzvf mlterm-3.1.1.tar.gz ; cd mlterm-3.1.1
 $ ./configure --prefix=/opt/mlterm --enable-ind --enable-anti-alias
 $ make
 $ sudo make install
 $ vi ~/.mlterm/aafont
ISCII_HINDI = DV\-TTYogesh 23
 $ /opt/mlterm/bin/mlterm -E utf8 -w 16 -m --im=kbd:isciihindi --lsp 2 --bi=false --ind --type=xft

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

[Mlterm-dev-en] mlterm 3.1.1 released

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

 Hi,

 This is to announce the release of mlterm version 3.1.1

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

MD5 (mlterm-3.1.1.tar.gz) = a59ff4b32c4985fd2d1d5c3000cfc7b8
SHA1 (mlterm-3.1.1.tar.gz) = 011ad6e48a71463d16eb2a72ca180801a3dd67b1

Overview of changes from 3.1.0
===============================

ver 3.1.1
* Fix a bug which caused segfault in 64bit Linux.
* Enable to change 0-15 colors by OSC 4 sequence.
* Enable to specify --sep, --button3, --clip, --restart and --logmsg options
  for mlclient.
--
Araki Ken
ara...@us...

Re: [Mlterm-dev-en] 3.1.0 crash

[Andi C. S. <ski...@ya...>]

I patched it, built it and it runs now; I am very grateful for your time in implementing these. I have tested them, but have found that they work only partially: the change only takes effect if it doesn't conflict with another attribute (with bold cancelling ul_color and reverse-video cancelling both bd_color and ul_color).

To illustrate (having set bg_color = black, fg_color = white, bd_color = hl_white and ul_color = cyan), BD and UL appear as expected, but BD + UL is underlined hl_white on black (i.e. ul_color/disable underline has no effect) and RV + anything else is black on white (plus the other attributes), just as if bd_color and ul_color were not defined (although they behave as expected when selected with the mouse).

I think these conflicts should be solved by making ul_color only set the colour of UL text, and adding a separate option to disable every instance of the underline (including coloured text), a second one to disable BD text (again, for all cases) and a third one (let's say bu_color) to choose a colour for text which is BD + UL. Also, reverse-video should take into account the actual colour of the text after setting these options.

Re: [Mlterm-dev-en] 3.1.0 crash

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

 Hi,

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: [Mlterm-dev-en] 3.1.0 crash
Date: Mon, 23 Apr 2012 09:14:42 -0700 (PDT)
Message-ID: <133...@we...>

> I wanted to try out the new options (bd_color, ul_color etc.); I built mlterm-3.1.0, but it won't run.

 I'm sorry but mlterm 3.1.0 has a bug causing segmentation fault in 64bit Linux.
 Please apply an attached patch to mlterm-3.1.0 and rebuild before trying
bd_color and ul_color options.

 I'll release 3.1.1 to fix this problem.

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

[Mlterm-dev-en] 3.1.0 crash

[Andi C. S. <ski...@ya...>]

Hello,

I wanted to try out the new options (bd_color, ul_color etc.); I built mlterm-3.1.0, but it won't run.

I was wondering, though, if bd_color will also disable bold style and how will text that is both bold AND underlined display (is there a separate option to control it or will one option take precedence over the other?).

I configured it with --enable-debug to see what happens and then installed as usual, and on launching it crashes.

I'm running Linux 3.2.12-gentoo on x86_64, with gcc-4.5.3 and glibc-2.14.1-r3 (from Gentoo Portage).

Here's what I got from gdb:

(gdb) run
Starting program: /usr/local/bin/mlterm 
WARN: [kik_conf.c:661] no such key[logging_msg] in conf map.
 0x443ccd is freed at x_xim_final[l.394 in ../xwindow/xlib/x_xim.c] but not logged.
*** glibc detected *** /usr/local/bin/mlterm: munmap_chunk(): invalid pointer: 0x0000000000443ccd ***
======= Backtrace: =========
/lib64/libc.so.6(+0x76516)[0x7ffff6f48516]
/usr/local/bin/mlterm[0x4322b4]
/usr/local/bin/mlterm[0x40c4a6]
/usr/local/bin/mlterm[0x40c565]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7ffff6ef42ad]
/usr/local/bin/mlterm[0x40b6c9]
======= Memory map: ========
00400000-00458000 r-xp 00000000 08:01 19843                              /usr/local/bin/mlterm
00657000-00658000 r--p 00057000 08:01 19843                              /usr/local/bin/mlterm
00658000-0065a000 rw-p 00058000 08:01 19843                              /usr/local/bin/mlterm
0065a000-006bd000 rw-p 00000000 00:00 0                                  [heap]
7ffff6691000-7ffff66a6000 r-xp 00000000 08:01 2151669955                 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libgcc_s.so.1
7ffff66a6000-7ffff68a6000 ---p 00015000 08:01 2151669955                 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libgcc_s.so.1
7ffff68a6000-7ffff68a7000 r--p 00015000 08:01 2151669955                 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libgcc_s.so.1
7ffff68a7000-7ffff68a8000 rw-p 00016000 08:01 2151669955                 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libgcc_s.so.1
7ffff68a8000-7ffff68ad000 r-xp 00000000 08:01 2147518354                 /usr/lib64/libXdmcp.so.6.0.0
7ffff68ad000-7ffff6aac000 ---p 00005000 08:01 2147518354                 /usr/lib64/libXdmcp.so.6.0.0
7ffff6aac000-7ffff6aad000 r--p 00004000 08:01 2147518354                 /usr/lib64/libXdmcp.so.6.0.0
7ffff6aad000-7ffff6aae000 rw-p 00005000 08:01 2147518354                 /usr/lib64/libXdmcp.so.6.0.0
7ffff6aae000-7ffff6ab0000 r-xp 00000000 08:01 2147516186                 /usr/lib64/libXau.so.6.0.0
7ffff6ab0000-7ffff6cb0000 ---p 00002000 08:01 2147516186                 /usr/lib64/libXau.so.6.0.0
7ffff6cb0000-7ffff6cb1000 r--p 00002000 08:01 2147516186                 /usr/lib64/libXau.so.6.0.0
7ffff6cb1000-7ffff6cb2000 rw-p 00003000 08:01 2147516186                 /usr/lib64/libXau.so.6.0.0
7ffff6cb2000-7ffff6cd1000 r-xp 00000000 08:01 2147584961                 /usr/lib64/libxcb.so.1.1.0
7ffff6cd1000-7ffff6ed0000 ---p 0001f000 08:01 2147584961                 /usr/lib64/libxcb.so.1.1.0
7ffff6ed0000-7ffff6ed1000 r--p 0001e000 08:01 2147584961                 /usr/lib64/libxcb.so.1.1.0
7ffff6ed1000-7ffff6ed2000 rw-p 0001f000 08:01 2147584961                 /usr/lib64/libxcb.so.1.1.0
7ffff6ed2000-7ffff7057000 r-xp 00000000 08:01 382832                     /lib64/libc-2.14.1.so
7ffff7057000-7ffff7257000 ---p 00185000 08:01 382832                     /lib64/libc-2.14.1.so
7ffff7257000-7ffff725b000 r--p 00185000 08:01 382832                     /lib64/libc-2.14.1.so
7ffff725b000-7ffff725c000 rw-p 00189000 08:01 382832                     /lib64/libc-2.14.1.so
7ffff725c000-7ffff7261000 rw-p 00000000 00:00 0 
7ffff7261000-7ffff739f000 r-xp 00000000 08:01 2147492192                 /usr/lib64/libX11.so.6.3.0
7ffff739f000-7ffff759f000 ---p 0013e000 08:01 2147492192                 /usr/lib64/libX11.so.6.3.0
7ffff759f000-7ffff75a0000 r--p 0013e000 08:01 2147492192                 /usr/lib64/libX11.so.6.3.0
7ffff75a0000-7ffff75a5000 rw-p 0013f000 08:01 2147492192                 /usr/lib64/libX11.so.6.3.0
7ffff75a5000-7ffff75a7000 r-xp 00000000 08:01 382965                     /lib64/libdl-2.14.1.so
7ffff75a7000-7ffff77a7000 ---p 00002000 08:01 382965                     /lib64/libdl-2.14.1.so
7ffff77a7000-7ffff77a8000 r--p 00002000 08:01 382965                     /lib64/libdl-2.14.1.so
7ffff77a8000-7ffff77a9000 rw-p 00003000 08:01 382965                     /lib64/libdl-2.14.1.so
7ffff77a9000-7ffff77c4000 r-xp 00000000 08:01 2147745376                 /usr/local/lib64/libmkf.so.16.0.0
7ffff77c4000-7ffff79c3000 ---p 0001b000 08:01 2147745376                 /usr/local/lib64/libmkf.so.16.0.0
7ffff79c3000-7ffff79c4000 r--p 0001a000 08:01 2147745376                 /usr/local/lib64/libmkf.so.16.0.0
7ffff79c4000-7ffff79c6000 rw-p 0001b000 08:01 2147745376                 /usr/local/lib64/libmkf.so.16.0.0
7ffff79c6000-7ffff79d1000 r-xp 00000000 08:01 2147742549                 /usr/local/lib64/libkik.so.14.0.1
7ffff79d1000-7ffff7bd1000 ---p 0000b000 08:01 2147742549                 /usr/local/lib64/libkik.so.14.0.1
7ffff7bd1000-7ffff7bd2000 r--p 0000b000 08:01 2147742549                 /usr/local/lib64/libkik.so.14.0.1
7ffff7bd2000-7ffff7bd3000 rw-p 0000c000 08:01 2147742549                 /usr/local/lib64/libkik.so.14.0.1
7ffff7bd3000-7ffff7bdb000 r-xp 00000000 08:01 2147745451                 /usr/local/lib64/libmlterm_core.so
7ffff7bdb000-7ffff7dda000 ---p 00008000 08:01 2147745451                 /usr/local/lib64/libmlterm_core.so
7ffff7dda000-7ffff7ddb000 r--p 00007000 08:01 2147745451                 /usr/local/lib64/libmlterm_core.so
7ffff7ddb000-7ffff7ddc000 rw-p 00008000 08:01 2147745451                 /usr/local/lib64/libmlterm_core.so
7ffff7ddc000-7ffff7dfd000 r-xp 00000000 08:01 382843                     /lib64/ld-2.14.1.so
7ffff7e5a000-7ffff7fe3000 r--p 00000000 08:01 383571                     /usr/lib64/locale/locale-archive
7ffff7fe3000-7ffff7fe8000 rw-p 00000000 00:00 0 
7ffff7ff1000-7ffff7ff8000 r--s 00000000 08:01 383551                     /usr/lib64/gconv/gconv-modules.cache
7ffff7ff8000-7ffff7ffb000 rw-p 00000000 00:00 0 
7ffff7ffb000-7ffff7ffc000 r-xp 00000000 00:00 0                          [vdso]
7ffff7ffc000-7ffff7ffd000 r--p 00020000 08:01 382843                     /lib64/ld-2.14.1.so
7ffff7ffd000-7ffff7ffe000 rw-p 00021000 08:01 382843                     /lib64/ld-2.14.1.so
7ffff7ffe000-7ffff7fff000 rw-p 00000000 00:00 0 
7ffffffde000-7ffffffff000 rw-p 00000000 00:00 0                          [stack]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]

Program received signal SIGABRT, Aborted.
0x00007ffff6f07b45 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff6f07b45 in raise () from /lib64/libc.so.6
#1  0x00007ffff6f08fc6 in abort () from /lib64/libc.so.6
#2  0x00007ffff6f42fe7 in ?? () from /lib64/libc.so.6
#3  0x00007ffff6f48516 in ?? () from /lib64/libc.so.6
#4  0x00000000004322b4 in x_xim_final () at ../xwindow/xlib/x_xim.c:394
#5  0x000000000040c4a6 in main_loop_final () at main_loop.c:437
#6  0x000000000040c565 in main (argc=1, argv=0x7fffffffe248) at main.c:75

I hope it will be of some help.

Andi Șerbănescu

Re: [Mlterm-dev-en] mlterm with Devanagari

[Mayuresh <may...@ac...>]

On Mon, Apr 02, 2012 at 09:46:29PM +0900, Araki Ken wrote:
> > Here are mine, though not exactly matching, the ones you mentioned
> > specifically are there:
> 
>  I think necessary modules are correctly installed.

For sake of a try, I upgraded to 3.1.0, though Devanagari continues to not
work on my terminal.

Does my OS matter? It is NetBSD 6.0 BETA.

Mayuresh.

Re: [Mlterm-dev-en] Feature request

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

 Hi,

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: Re: [Mlterm-dev-en] Feature request
Date: Thu, 12 Apr 2012 08:53:28 -0700 (PDT)
Message-ID: <133...@we...>

> >>5. An option to display text with attributes (bold and underline) in colour instead.
>
> > Could you tell me more about how the option works ?
> 
> This one essentially emulates the console's behaviour. Instead of drawing the thin line beneath underlined characters, they would be displayed in a colour of the user's choice (let's call it ul_color).
> 
> Likewise, instead of bold fonts, bright colours would be used, including for fg_color and ul_color, provided they're set to one of the 8 non-bright colours in ~/.mlterm/color. Bright colours are already used, but not for plain FG and without the option to disable bold fonts.
> 
> It may be easier to implement these options independently, i.e. one each for disabling bold text, disabling the underline, setting ul_color and using bright colours for fg_color and ul_color too (and maybe not using them at all).
> 
> This is mostly due to personal preference, but sometimes text that is both bold and bright (and/or underlined) provides too much emphasis, so using a single font style/weight would be less distracting.

 Thanks.

 I added "ul_color" and "bd_color" options in mlterm-3.0.11.
 Please test it.

(Usage) ~/.mlterm/main
ul_color = (Specify color you want to show instead of underline.)
---
Araki Ken
ara...@us...

[Mlterm-dev-en] mlterm 3.1.0 released

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

 Hi,

 This is to announce the release of mlterm version 3.1.0

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

MD5 (mlterm-3.1.0.tar.gz) = 6bb3d176cbcbcb2427ac1a67615a63f3
SHA1 (mlterm-3.1.0.tar.gz) = a2ae874d447856a66db69f14078a1eca934479e6

Overview of changes from 3.0.11
===============================

ver 3.1.0
* Support extended mouse tracking mode. (CSI ? 1005 h and CSI ? 1005 l)
* Support "use_variable_column_width" and "letter_space" options in win32.
* Support multiple numeric parameters of SM, RM, DECSET and DESRST sequence.
  (Thanks to Iwamoto Kouichi san)
* Support BiDi mirroring. (Thanks to Khaled Hosny)
* Add "blink_cursor" option.
* Add "inner_border" option.
* Add "bd_color"(rxvt style) and "ul_color" options. (equivalent to colorBD and colorUL
  options of xterm and rxvt.)
* Add "cipher_list" for ssh connection.
* Add java version. (experimental)
* Add VT52 emulation. (configure with --enable-vt52 option.)
* Remove IIIMF plugin.
* Bug fixes:
  SF Bug #2878878 (Thanks to Kusanagi Kouichi san)
  SF Bug #3481552 (Thanks to Kobayashi Hiroaki san)
  SF Bug #3487163 (Thanks to raghavkrishna)
  SF Bug #3509743 (Thanks to Thomas Wolff)
  SF Bug #3509744 (Thanks to Thomas Wolff)
  SF Bug #3512067 (Thanks to phcoder)
  Fix a bug which didn't clear margin area after visual bell.
  Fix a bug which disabled scrolling in vertical mode in win32.
  Fix a bug which disabled wheel mouse in win32.
  Fix a bug of reverse-video algorithm of highlighted cursor or selected text.
  (Thanks to Andi Cristian Serbanescu)

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

Re: [Mlterm-dev-en] Feature request

[Andi C. S. <ski...@ya...>]

>>5. An option to display text with attributes (bold and underline) in colour instead.

>
>Could you tell me more about how the option works ?

This one essentially emulates the console's behaviour. Instead of drawing the thin line beneath underlined characters, they would be displayed in a colour of the user's choice (let's call it ul_color).

Likewise, instead of bold fonts, bright colours would be used, including for fg_color and ul_color, provided they're set to one of the 8 non-bright colours in ~/.mlterm/color. Bright colours are already used, but not for plain FG and without the option to disable bold fonts.

It may be easier to implement these options independently, i.e. one each for disabling bold text, disabling the underline, setting ul_color and using bright colours for fg_color and ul_color too (and maybe not using them at all).

This is mostly due to personal preference, but sometimes text that is both bold and bright (and/or underlined) provides too much emphasis, so using a single font style/weight would be less distracting.


> Fixes above is pushed hg repository at sf.net.

Thank you for the other fixes. I built it, but for some reason the binary doesn't do anything. I didn't experiment any further to see if it might work, though. I'll try doing it during the following days.

Andi Șerbănescu

Re: [Mlterm-dev-en] Feature request

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

 Hi,

From: Andi Cristian Serbanescu <ski...@ya...>
Subject: [Mlterm-dev-en] Feature request
Date: Wed, 4 Apr 2012 04:04:37 -0700 (PDT)
Message-ID: <133...@we...>

> 1. Set the width of the internal border (it's 2 pixels wide and can't be configured as far as I know);

 I supported it. Specify "inner_border = value" in ~/.mlterm/main or
"--border=value" as a command line argument.

> 2. Simplify the cursor's reverse-video algorithm. If the character cell underneath has bright text, then the resulting cursor foreground is also bright, regardless of the cell's background originally being bright or not (e.g. hl_black on yellow becomes hl_yellow on hl_black), which looks bad and can lead to poor visibility sometimes. What we want is to simply swap the background and foreground colours (so that the earlier example would become yellow on hl_black).
> 3. The same behaviour for highlighted text (i.e. with the mouse);

 I fixed it. 

> 4. Make the cursor blink:)

 I supported it. Specify "blink_cursor = true" in ~/.mlterm/main or
"--blink" as a command line argument.


 Fixes above is pushed hg repository at sf.net.


> 5. An option to display text with attributes (bold and underline) in colour instead.

 Could you tell me more about how the option works ?

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

[Mlterm-dev-en] Feature request

[Andi C. S. <ski...@ya...>]

Hello,

This is a feature request. I didn't know where to send it, so I thought it should go here. I have mlterm and works well for me, yet there are a few minor things which would be nice to have:

1. Set the width of the internal border (it's 2 pixels wide and can't be configured as far as I know);


2. Simplify the cursor's reverse-video algorithm. If the character cell underneath has bright text, then the resulting cursor foreground is also bright, regardless of the cell's background originally being bright or not (e.g. hl_black on yellow becomes hl_yellow on hl_black), which looks bad and can lead to poor visibility sometimes. What we want is to simply swap the background and foreground colours (so that the earlier example would become yellow on hl_black).


3. The same behaviour for highlighted text (i.e. with the mouse);


4. Make the cursor blink:)


5. An option to display text with attributes (bold and underline) in colour instead.

Re: [Mlterm-dev-en] mlterm with Devanagari

[Mayuresh <may...@ac...>]

On Mon, Apr 02, 2012 at 09:46:29PM +0900, Araki Ken wrote:
>  Does following commands change appearance of mlterm ?
> 
> $ mlcc use_bidi false
> $ mlcc use_ind false
> $ mlcc use_ind true

No difference seen. Please check the following steps. Is that what you
wanted to check?

I opened mlterm with environment variable  LANG=en_US.UTF-8.

After that I ran above 3 commands in a row,

After that I launched elinks to visit a Devanagari site mentioned before.

Mayuresh.