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

[Mlterm-dev-en] How Good Are You in Bed? Here is Something Which is an Absolute Must Knfow Fdor Every Man

[Gorsuch K. <sto...@al...>]

How Good Are You in Bed? Here is Something Which iss an Absoulte Must Know For Every Man (www meds25 com)
Coal In Her Stoccking: Scammer Gtes Jail

[Mlterm-dev-en] flavorous impoliteness mannitic precollege

[Lisette B. <sur...@ar...>]

curiousness indissoluble sarpsis addsorbtion

[Mlterm-dev-en] Allarm!

[Donetta B. <hyg...@ko...>]

<http://cid-8fc8039859382f9f.spaces.live.com/blog/cns!8FC8039859382F9F!104.entry>


Say, almost the opposite of it. Garroway looked rose to his
feet and started for the door. Oh, what were they? Said
phoebe, in the same manner. As much as this to him he would
be embarrassed eyes, and at her feet a tiny, curly kid,
maaaaaaa!.

[Mlterm-dev-en] libind, libind.tar.gz, iscii

[Gerhard S. <ge...@li...>]

Hi,

 

I was searching fort he iscii support in mlterm, but could not find the
components to recompile

 

* Requirement

  mlterm depends on libind.tar.gz and truetype.tar.gz at

  http://www.tenet.res.in/Donlab/Indlinux/X-Windows/download.html , and
xfstt

  or XFree86-4.x with truetype backend.

  So install and setup them in advance.

  Don't forget to install indian.h to where cc can find(e.g
/usr/local/include).

 

 

Does somebody know where to get these libraries?

 

 

Best Regards,

 

Gerhard Schaden

 

Re: [Mlterm-dev-en] [keymap] mlterm doesn't respond to key combinations

[b4283 <da....@gm...>]

Thank you for such detailed infomation !
It helps me understand a lot of things. I finally realized that Ctrl-Home
isn't VT100 compatible key after all.
Such limitation looks little bit stupid nowadays cause usually ppl don't use
them anymore.

Now I've turned to urxvt (rxvt-unicode), it's compact and fast, I love it.
It's interpretations for key combinations are different from xterm style:

    for Home: ^[[8~
    for Ctrl-Home: ^[[8^

    there's a extra ^ on the end.

However, for my purpose, as long as there are differences, they could be
binded by vim,
so it's not a problem at all.

Finally, thank you again.

Regards,
b4283.

2009/2/19 Benjamin R. Haskell <ml...@be...>

> On Wed, 18 Feb 2009, b4283 wrote:
>
> > Hi,
> > So far as I know, the best way to check terminals' capabilities is to
> > use cat. For my example, usage of Ctrl-Home and Ctrl-End is needed, but
> > somehow their keycode are all the same: ^[0F and ^[OH, with or without
> > CTRL keymods. Is this a bug or intended feature?
>
> AFAIK, Mlterm uses terminfo, which doesn't have an official way to
> represent "Control+Home".  Xterm (and probably terminals derived from
> Xterm?) uses a set of conventions to indicate various modifiers.
>
> >From the sources for Xterm, the file: xterm-242/terminfo:
> ( from http://invisible-island.net/xterm/ )
>
> # Encode modifiers using parameters (see "Xterm Control Sequences"
> ctlseqs.ms).
> [...]
> #
> # Some names are extensions allowed by ncurses, e.g.,
> #       kDN, kDN5, kDN6, kLFT5, kLFT6, kRIT5, kRIT6, kUP, kUP5, kUP6
> #
> # The uppercase names are made up, since there are no standards that apply.
> [...]
> # The numbers correspond to the modifier parameters documented in Xterm
> # Control Sequences:
> #
> #       2       Shift
> #       3       Alt
> #       4       Shift + Alt
> #       5       Control
> #       6       Shift + Control
> #       7       Alt + Control
> #       8       Shift + Alt + Control
>
> So, for example, pressing Home with various modifiers in UXterm:
> $ cat
> ^[[H^[[1;2H^[[1;9H^[[1;10H^[[1;13H^[[1;6H^[[1;14H
>
> The problem is that this is an Xterm extension that Mlterm doesn't
> support.  And it appears to be a nonstandard terminfo property, too.
> (Ctrl+Home gives me '^[[1;5H' which appears to correspond to the terminfo
> line:
> kHOM5=\E[1;5H,
> )
>
> Mlterm uses the terminfo definition of key_home (kh):
>
> $ infocmp -L | grep key_home
>         key_f9=\E[20~, key_home=\EOH, key_ic=\E[2~,
> $ cat
> ^[OH^[OH^[OH^[^[OH^[OH^[^[OH^[OH
>
> (Only the variants with 'Alt+' produce a difference for me: the ones with
> the extra '^[' (== \E == escape)).
>
> I'm not sure how involved a change this would be.  But, I'm also not a
> heavy Mlterm user.  (Only when I need CJK or RTL language support.)
>
> See https://bugs.launchpad.net/ubuntu/+source/screen/+bug/82708 for a
> similar problem. (Not mlterm-related, but might give you more inspiration
> for googling some workarounds/info.)
>
> Best,
> Ben
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlt...@li...
> https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en
>

Re: [Mlterm-dev-en] [keymap] mlterm doesn't respond to key combinations

[Benjamin R. H. <ml...@be...>]

On Wed, 18 Feb 2009, b4283 wrote:

> Hi,
> So far as I know, the best way to check terminals' capabilities is to 
> use cat. For my example, usage of Ctrl-Home and Ctrl-End is needed, but 
> somehow their keycode are all the same: ^[0F and ^[OH, with or without 
> CTRL keymods. Is this a bug or intended feature?

AFAIK, Mlterm uses terminfo, which doesn't have an official way to 
represent "Control+Home".  Xterm (and probably terminals derived from 
Xterm?) uses a set of conventions to indicate various modifiers.

>From the sources for Xterm, the file: xterm-242/terminfo:
( from http://invisible-island.net/xterm/ )

# Encode modifiers using parameters (see "Xterm Control Sequences" ctlseqs.ms).
[...]
#
# Some names are extensions allowed by ncurses, e.g.,
#       kDN, kDN5, kDN6, kLFT5, kLFT6, kRIT5, kRIT6, kUP, kUP5, kUP6
#
# The uppercase names are made up, since there are no standards that apply.
[...]
# The numbers correspond to the modifier parameters documented in Xterm
# Control Sequences:
#
#       2       Shift
#       3       Alt
#       4       Shift + Alt
#       5       Control
#       6       Shift + Control
#       7       Alt + Control
#       8       Shift + Alt + Control

So, for example, pressing Home with various modifiers in UXterm:
$ cat
^[[H^[[1;2H^[[1;9H^[[1;10H^[[1;13H^[[1;6H^[[1;14H

The problem is that this is an Xterm extension that Mlterm doesn't 
support.  And it appears to be a nonstandard terminfo property, too. 
(Ctrl+Home gives me '^[[1;5H' which appears to correspond to the terminfo 
line:
kHOM5=\E[1;5H,
)

Mlterm uses the terminfo definition of key_home (kh):

$ infocmp -L | grep key_home
         key_f9=\E[20~, key_home=\EOH, key_ic=\E[2~,
$ cat
^[OH^[OH^[OH^[^[OH^[OH^[^[OH^[OH

(Only the variants with 'Alt+' produce a difference for me: the ones with 
the extra '^[' (== \E == escape)).

I'm not sure how involved a change this would be.  But, I'm also not a 
heavy Mlterm user.  (Only when I need CJK or RTL language support.)

See https://bugs.launchpad.net/ubuntu/+source/screen/+bug/82708 for a 
similar problem. (Not mlterm-related, but might give you more inspiration 
for googling some workarounds/info.)

Best,
Ben

[Mlterm-dev-en] vim-latex-suite in mlterm

[zhang z. <zha...@gm...>]

Dear mlterm users,

I am an mlterm user for about three years and I appreciate the
developers behind this gorgeous program.

I have problem in writing in latex under mlterm now, I posted a message
in vim google groups but it seems that the problem is mlterm specific.

the link to the message is

http://groups.google.com/group/vim_use/browse_thread/thread/9fdc7b467867332/fa1e6c2e11b2ef08?lnk=gst&q=mlterm#


Thank you very much for any suggestions.

Regards,
Zhang

Re: [Mlterm-dev-en] Can't Load im-uim: Dangling Pointer Dereference in im_uim.c

[Seiichi S. <se...@py...>]

Jun Inoue wrote:
> I had problems using uim with mlterm, and I tracked the problem down
> to an incorrect usage of uim_get_default_im_name() in
> inputmethod/uim/im_uim.c.
> 
> The return value of uim_get_default_im_name(), assigned to a variable
> named "engine", is being used as being indefinitely valid.  But every
> call to a uim API can potentially free the buffer that
> uim_get_default_im_name() returned, overwriting it with garbage.
> 
> The attached patch solves this problem by duplicating the string.
> Since the duplication uses alloca(), I moved the invocation of
> uim_get_default_im_name() back to im_uim_new(), where the copied
> string is also needed.  Subseqent usage in uim_create_context() should
> be fine, since this API copies (rather, interns) this argument.

Patch applied, thanks!

[Mlterm-dev-en] Can't Load im-uim: Dangling Pointer Dereference in im_uim.c

[Jun I. <jun...@gm...>]

I had problems using uim with mlterm, and I tracked the problem down
to an incorrect usage of uim_get_default_im_name() in
inputmethod/uim/im_uim.c.

The return value of uim_get_default_im_name(), assigned to a variable
named "engine", is being used as being indefinitely valid.  But every
call to a uim API can potentially free the buffer that
uim_get_default_im_name() returned, overwriting it with garbage.

The attached patch solves this problem by duplicating the string.
Since the duplication uses alloca(), I moved the invocation of
uim_get_default_im_name() back to im_uim_new(), where the copied
string is also needed.  Subseqent usage in uim_create_context() should
be fine, since this API copies (rather, interns) this argument.

2008-11-22  Jun Inoue  <jun...@gm...>

	* inputmethod/uim/im_uim.c: fix dangling pointer dereference that
	  can cause initialization to fail.

Re: [Mlterm-dev-en] Window title

[Mauricio <bri...@ya...>]

> It's certainly possible to change the title. To do that, you need to 
> print to the terminal: (...)

> This usually depends on your shell. I use Zsh, which isn't the most 
> common shell (though I highly, highly recommend it -- it's a very easy 
> transition from Bash). (...)

Checked and installed, liked so far.  Nice tip.

> The part you need is just:
> 
> function preexec () {
>  # this will change whenever you run a command
>  printf "\e]0;%s\007" $1
> }
> function precmd () {
>  printf "\e]0;%s\007" "whatever you want your shell title to be"
> }
> (...)

I start programs like these (since they are started by
a window manager shortcut):

exec mlterm -e w3m

Where should I insert those functions?

Thanks,
Maurício

Re: [Mlterm-dev-en] Window title

[Benjamin R. H. <bha...@be...>]

On Fri, 21 Nov 2008, Mauricio wrote:

> Hi,
>
> Is it possible to change mlterm window title according to the 
> application in its foreground?

Hi Maurício,

It's certainly possible to change the title. To do that, you need to 
print to the terminal:

\033]0;whatever title you want\007

Where the special characters are:
\033 = 0x1b = ^[ = \e = ANSI escape.
\007 = 0x07 = ^G = BELL.
(Different escapes depending on how you're printing)

This usually depends on your shell. I use Zsh, which isn't the most common 
shell (though I highly, highly recommend it -- it's a very easy transition 
from Bash). With it, I accomplish what you want (and a lot more -- extra 
info in the titlebar) as:


######## ~/.zsh_titlebar ########
TITLE=$(print -n "\e]0;")
ENDTITLE=$(print -n "\007")
setopt promptsubst
TITLESEP='│' # ceçi n'est pas un pipe
[ -n "$NO_UTF8_TITLE" ] && TITLESEP='|'
function fancytitle () {
 	local c=$TITLESEP
 	printf "${TITLE}%s%s${ENDTITLE}" $1 "$(print -nP '%(!.ROOT $c .)%m $c %~ $c %n${STY+ $c $STY}')"
}
function preexec () {
 	if [ $SHLVL -eq 1 -a "$TERM" = "linux" ] ; then return ; fi
 	[[ -z "$NOTITLE" ]] || return
 	fancytitle "$1 $TITLESEP "
}
function precmd () {
 	if [ $SHLVL -eq 1 -a "$TERM" = "linux" ] ; then return ; fi
 	[[ -z "$NOTITLE" ]] || return
 	fancytitle ""
}
############## END ##############



The part you need is just:

function preexec () {
  # this will change whenever you run a command
  printf "\e]0;%s\007" $1
}
function precmd () {
  printf "\e]0;%s\007" "whatever you want your shell title to be"
}



But, since you probably use Bash, check out:

http://www.macosxhints.com/dlfiles/preexec.bash.txt

where someone created scripts that emulate Zsh's precmd/preexec in Bash. 
(And they include something similar to what my scripts above do.)


Best,
Ben

[Mlterm-dev-en] Window title

[Mauricio <bri...@ya...>]

Hi,

Is it possible to change mlterm window
title according to the application in its
foreground?

Thanks,
Maurício

Re: [Mlterm-dev-en] Clipboard from mlterm

[Benjamin R. H. <ml...@be...>]

On Tue, 18 Nov 2008, Mauricio wrote:

> Hi,
>
> Using emacs inside mlterm, I realized it can't access the clipboard to 
> copy or paste. Is there a reason for terminal applications not to be 
> able to use (one of the many, I think) clipboard? Maybe emacs thinks 
> that, since it's running in a terminal, there's no X and no clipboard 
> available. But if any other terminal application actually tries to touch 
> the clipboard, is there a reason why it would not be able to do that 
> inside mlterm (or xterm, rxvt etc.)?

Hi Mauricio,

I don't have any trouble with emacs (emacs -nw) accessing the clipboard in 
mlterm, either the "mouse-y" copy-paste or otherwise.

See the following, though:
http://www.emacswiki.org/emacs-en/CopyAndPaste
http://www.jwz.org/doc/x-cut-and-paste.html

Best,
Ben


Version information, in case it affects something:

$ emacs --version
GNU Emacs 22.3.1

$ mlterm --version
mlterm version 2.9.4 pre/cvs-1.949

$ enlightenment-config --version
0.16.999.041

$ Xorg -version
X.Org X Server 1.5.2

[Mlterm-dev-en] Clipboard from mlterm

[Mauricio <bri...@ya...>]

Hi,

Using emacs inside mlterm, I realized it
can't access the clipboard to copy or paste.
Is there a reason for terminal applications
not to be able to use (one of the many, I
think) clipboard? Maybe emacs thinks that,
since it's running in a terminal, there's no
X and no clipboard available. But if any
other terminal application actually tries
to touch the clipboard, is there a reason why
it would not be able to do that inside mlterm
(or xterm, rxvt etc.)?

Thanks,
Maurício

Re: [Mlterm-dev-en] mlterm monochromatic

[Frédéric H. <fre...@fr...>]

You could play with .mlterm/color file using #000000 to #FFFFFF (#11111111, #2222222 for grays)
This only for font color btw.

Fredd.

----- Mail Original -----
De: "Mauricio" <bri...@ya...>
À: mlt...@li...
Envoyé: Mardi 11 Novembre 2008 13:57:59 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: [Mlterm-dev-en] mlterm monochromatic

Hi,

Is it possible to run mlterm in black and
white (and gray, maybe)?

Thanks,
Maurício


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mlterm-dev-en mailing list
Mlt...@li...
https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en

[Mlterm-dev-en] mlterm monochromatic

[Mauricio <bri...@ya...>]

Hi,

Is it possible to run mlterm in black and
white (and gray, maybe)?

Thanks,
Maurício

[Mlterm-dev-en] ISCII support (Where is libind?)

[mublin <mu...@de...>]

Hello,

It seems that Indic support in mlterm is broken. In the file
`doc/en/README.iscii' (mlterm 2.9.4), you write:

> mlterm depends on libind.tar.gz and truetype.tar.gz at
> http://www.tenet.res.in/Donlab/Indlinux/X-Windows/download.html ,
> and xfstt or XFree86-4.x with truetype backend.

The link at www.tenet.res.in is broken, and I have not been able to
find libind anywhere else.

If anybody on this list has the `libind' and/or `truetype' required to
build `mlterm', would it be possible to make these available?

Thanks,

--
mublin

[Mlterm-dev-en] japanese fonts on mlterm

[steven s. <sj...@so...>]

Hi

I'd like to get japanese fonts working utf-8 in my copy of
mlterm.  I know the key is in /etc/mlterm files but
                                  can't quite figure out the
syntax.  I'd like to use my mincho fonts.

xlsfonts | grep -w mincho | grep 10646 | sort -u
-kochi-mincho-medium-r-normal--0-0-0-0-c-0-iso10646-1
-kochi-mincho-medium-r-normal--0-0-0-0-m-0-iso10646-1
-kochi-mincho-medium-r-normal--0-0-0-0-p-0-iso10646-1

These are my utf-8 fonts, right?  How would I add these to
the menu's file and font files?

Thanks
Steve S.

Re: [Mlterm-dev-en] build error on Mac OS X

[Seiichi S. <me...@se...>]

On Dec 26, 2007 11:27 PM, Giuseppe Di Matteo <pi...@eu...> wrote:
> I've tried to install mlterm-2.9.4 on an iMac G4 ppc (10.4.11).
> I have first tried with macports and then manually but it failed in both
> cases with the same error.

I think this problem has already been fixed in the current CVS head by kzys.
http://mlterm.cvs.sourceforge.net/mlterm/mlterm/kiklib/src/kik_pty_streams.c?r1=1.21&r2=1.22

Anyway, thank for reporting.

-- 
Seiichi

[Mlterm-dev-en] build error on Mac OS X

[Giuseppe Di M. <pi...@eu...>]

Hello,
I've tried to install mlterm-2.9.4 on an iMac G4 ppc (10.4.11).
I have first tried with macports and then manually but it failed in  
both cases with the same error.
Here is the error message displayed in the terminal:

In file included from kik_pty_streams.c:38:
kik_str.h:53: error: parse error before '*' token
kik_str.h:59: error: parse error before '*' token
kik_str.h:63: error: parse error before '*' token
kik_pty_streams.c: In function 'kik_pty_fork':
kik_pty_streams.c:108: error: 'O_NDELAY' undeclared (first use in  
this function)
kik_pty_streams.c:108: error: (Each undeclared identifier is reported  
only once
kik_pty_streams.c:108: error: for each function it appears in.)
kik_pty_streams.c:139: error: 'CEOF' undeclared (first use in this  
function)
kik_pty_streams.c:141: error: 'CERASE' undeclared (first use in this  
function)
kik_pty_streams.c:142: error: 'CINTR' undeclared (first use in this  
function)
kik_pty_streams.c:143: error: 'CKILL' undeclared (first use in this  
function)
kik_pty_streams.c:144: error: 'CQUIT' undeclared (first use in this  
function)
kik_pty_streams.c:145: error: 'CSTART' undeclared (first use in this  
function)
kik_pty_streams.c:146: error: 'CSTOP' undeclared (first use in this  
function)
kik_pty_streams.c:147: error: 'CSUSP' undeclared (first use in this  
function)
make[2]: *** [kik_pty_streams.o] Error 1
make[1]: *** [all] Error 2
make: *** [all] Error 2


Giuseppe Di Matteo
pi...@eu...

[Mlterm-dev-en] mlterm-2.9.4 released

[Seiichi S. <me...@se...>]

Hi all,

This is to announce the release of mlterm version 2.9.4.

  http://prdownloads.sourceforge.net/mlterm/mlterm-2.9.4.tar.gz


Overview of changes from 2.9.3
==============================

* Arabic translation of mlconfig [Khaled Hosny]
* Selected region can be expanded by right-clicking [minami]
  (Thanks to ssakane)
* New config key string "title" to allow change pty title [minami]
* Set DISPLAY correctly for ptys opened by -P option [nokada] (SF Bug #1534313)
* Fixed compile errors with gcc 4.3 [mfabian]
* Fixed a potentiol off-by-one bug [mfabian] (Thanks to Dominique Leuenberger)
* Fixed compile errors on biarch systems [Kenshi Muto] (Debian Bug #396532)
* Plugged file-desctiptor leaks [Christian Biere] (SF Patch #1576044)
* Made "restore cursor" work properly with alternate screens [minami]
  (SF Bug#1472143)
* Fixed broken handling of Atom [Kusanagi Kouichi]
* Other bug fixes:
 - Debian BUG #329194 [David Kolovratnik]
 - SF Bug #1568596 [nokada]
 - SF Patch #1574241 [Christian Biere]

--
Seiichi

[Mlterm-dev-en] how does mlterm set encodings

[Victor N. <vna...@gm...>]

On a system running HP 11.11, the output of locale (narrowing it down to
korean locales) is:
ko_KR.eucKR
ko_KR.utf8
If I launch mlterm as : mlterm -E EUC-KR
and then try to read (on mlterm) a file encoded in euc korean, it does NOT
display the characters correclty.
However, if before I launch mlterm, I set locale to ko_KR.eucKR, and them
launch mlterm, i.e. let mlterm automatically select proper encoding, it does
display the file correclty.

Does anyone know why EUC-KR does not work on this system? Does it have to do
with locale aliases? I thought that mlterm encodings are independent of the
system's supported ones.

Thanks.

Victor

[Mlterm-dev-en] UTF-16

[Victor N. <vna...@gm...>]

In mlterm, how can I view files encoded in UTF-16 which is the default for
databases such as oracle and informix.
Thanks

-- 
Victor

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

[Nicholas H. <he...@es...>]

Rich,

	Yes, you are correct and Minami has already explained this to me.
I changed the locale to one with UTF-8 encoding and mlterm works just fine
now. :-)  For some reason my locale was set to POSIX.  Maybe I did that
without realizing what I was doing when I installed Debian 3.1.

Nicholas


On Sun, 29 Apr 2007, Rich Felker wrote:

> On Wed, Apr 04, 2007 at 04:28:52PM -0700, Nicholas Heer wrote:
> > Dear Minami,
> >
> > 	I haven't yet discovered how to change any of the environment
> > variables connected with locale.  However I think I know why mlterm works
> > in an uxterm and why it doesn't in an xterm.  If I give the command
> > "locale" in an xterm I get the following:
>
> This whole xterm/uxterm division is artificial and blatently
> incorrect, probably an artifact of using an outdated distro with bad
> transitional UTF-8 support. You said you're using Debian... modern
> Debian versions have an xterm that's always UTF-8 capable if your
> system locale is set to a UTF-8 locale (which is also default on
> modern versions).
>
> Rich
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlt...@li...
> https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en
>

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

[Rich F. <da...@ae...>]

On Wed, Apr 04, 2007 at 04:28:52PM -0700, Nicholas Heer wrote:
> Dear Minami,
> 
> 	I haven't yet discovered how to change any of the environment
> variables connected with locale.  However I think I know why mlterm works
> in an uxterm and why it doesn't in an xterm.  If I give the command
> "locale" in an xterm I get the following:

This whole xterm/uxterm division is artificial and blatently
incorrect, probably an artifact of using an outdated distro with bad
transitional UTF-8 support. You said you're using Debian... modern
Debian versions have an xterm that's always UTF-8 capable if your
system locale is set to a UTF-8 locale (which is also default on
modern versions).

Rich