"Alt Gr" key problem

Discussion:

Kiem Lam

2006-02-09 02:05:12 UTC

Hello,

I have just compiled and installed gvim 6.4 on HP-UX. It works really
nice but I am facing a problem with the "Alt Gr" key.

To be precise, in gvim, the "Alt Gr" key does not work in the Insert
mode and in the search pattern command (/word_to_search). However, it
works fine in the Command mode (:command). Moreover, I do not meet any
problem in vim (the problem only occurs in gvim). I am using a belgian
keyword.

For information, here is the content of my .gvimrc:

set guifont=-dec-terminal-medium-r-normal-*-*-140-*-*-c-*-iso8859-1

highlight Normal guibg=white
highlight NonText guibg=white

I tried to remove the font setting from the .gvimrc, but it does not
change anything. "magic" is set to default: on.

If anyone could help me out, it would be greatly appreciated!

Regards,

--
Kiem Lam

A. J. Mechelynck

2006-02-09 02:29:05 UTC

Permalink

Post by Kiem Lam
Hello,
I have just compiled and installed gvim 6.4 on HP-UX. It works really
nice but I am facing a problem with the "Alt Gr" key.
To be precise, in gvim, the "Alt Gr" key does not work in the Insert
mode and in the search pattern command (/word_to_search). However, it
works fine in the Command mode (:command). Moreover, I do not meet any
problem in vim (the problem only occurs in gvim). I am using a belgian
keyword.
set guifont=-dec-terminal-medium-r-normal-*-*-140-*-*-c-*-iso8859-1
highlight Normal guibg=white
highlight NonText guibg=white
I tried to remove the font setting from the .gvimrc, but it does not
change anything. "magic" is set to default: on.
If anyone could help me out, it would be greatly appreciated!
Regards,
--
Kiem Lam

8-O

I have a Belgian keyboard (fr_BE to be precise) and I have no problems
with it, neither in Vim nor in gvim.

1. Do you change the 'encoding' option somewhere (e.g., in your vimrc)?
If you do, try saving its value in 'termencoding', for instance as follows:

if &termencoding == ""
let &termencoding = &encoding
endif
set encoding=utf8
" etc.

2. Does it happen that you change the keyboard setting and/or language
using non-Vim OS tools ("International keyboard" widget et al.)? If it
does, especially while Vim is running, Vim (or gvim) is not aware of the
change and endless problems can happen.

3. "Normally" anything keyboard-related should by default work
identically in Insert/Replace and Command-line mode... unless you have
mappings for the one which do not affect the other. This brings a third
question:

Do you have cmap or imap (but not both) for some alt-keys (known in
mappings as <A- something > or <M- something >? Some Alt-keys are
indistinguishable to (g)vim from some accented characters from the
second half of the 8-bit ASCII set. Some of those accented characters
are obtained on the Belgian keyboard by Alt-Gr+something followed by
something (e.g., Alt-Gr+ù followed by E for capital-E-acute).

Best regards,
Tony.

Kiem Lam

2006-02-09 03:27:02 UTC

Permalink

Hello,

First of all, thanks for your answer.

Here are the few things I checked:

1. I do not change the "encoding" option anywhere.

2. So far, I do not think that I change the keyboard setting anywhere.

3. I checked my mappings but I do not think that the problem is coming
from them. I started vim and gvim with the following options:

vim -N -u NONE
gvim -N -u NONE

I exactly have the same behavior. It works perfectly in vim and I am
encoutering the same problems as the ones described in my previous
email in gvim.

Fo information, previously, I was using vim (and gvim) 5.7 in the same
environment and everything was working fine.

Regards,

Kiem

Post by A. J. Mechelynck

8-O
I have a Belgian keyboard (fr_BE to be precise) and I have no problems
with it, neither in Vim nor in gvim.
1. Do you change the 'encoding' option somewhere (e.g., in your vimrc)?
if &termencoding == ""
let &termencoding = &encoding
endif
set encoding=utf8
" etc.
2. Does it happen that you change the keyboard setting and/or language
using non-Vim OS tools ("International keyboard" widget et al.)? If it
does, especially while Vim is running, Vim (or gvim) is not aware of the
change and endless problems can happen.
3. "Normally" anything keyboard-related should by default work
identically in Insert/Replace and Command-line mode... unless you have
mappings for the one which do not affect the other. This brings a third
Do you have cmap or imap (but not both) for some alt-keys (known in
mappings as <A- something > or <M- something >? Some Alt-keys are
indistinguishable to (g)vim from some accented characters from the
second half of the 8-bit ASCII set. Some of those accented characters
are obtained on the Belgian keyboard by Alt-Gr+something followed by
something (e.g., Alt-Gr+ù followed by E for capital-E-acute).
Best regards,
Tony.

--
Kiem Lam

Kiem Lam

2006-02-13 08:29:53 UTC

Permalink

Hello,

I am still struggling my "Alt Gr" key in Gvim ;-( (belgian keyboard).
As explained in my previous emails, it does not work in Insert mode
and in the search pattern command (/string), but it works in the
command mode (:command). Moreover, it works just fine in vim.

If anybody could help me out, it would be greatly appreciated!

Regards,

Kiem

Post by Kiem Lam
Hello,
First of all, thanks for your answer.
1. I do not change the "encoding" option anywhere.
2. So far, I do not think that I change the keyboard setting anywhere.
3. I checked my mappings but I do not think that the problem is coming
vim -N -u NONE
gvim -N -u NONE
I exactly have the same behavior. It works perfectly in vim and I am
encoutering the same problems as the ones described in my previous
email in gvim.
Fo information, previously, I was using vim (and gvim) 5.7 in the same
environment and everything was working fine.
Regards,
Kiem

Post by A. J. Mechelynck

--
Kiem Lam

A. J. Mechelynck

2006-02-13 09:20:57 UTC

Permalink

Post by Kiem Lam
Hello,
I am still struggling my "Alt Gr" key in Gvim ;-( (belgian keyboard).
As explained in my previous emails, it does not work in Insert mode
and in the search pattern command (/string), but it works in the
command mode (:command). Moreover, it works just fine in vim.
If anybody could help me out, it would be greatly appreciated!
Regards,
Kiem

[...]

Well, I can't. Anyone on X11 who can reproduce this problem (accented
character keychords from Belgian keyboard using AltGr work OK in console
Vim and in command-line mode in gvim but not in Insert mode in gvim)?
The OP uses 6.4 (patchlevel unspecified) on HP-UX.

Note: AltGr is used a lot on the Belgian keyboard. See below; but first,
the keyboard layout (fixed-width font recommended):

³ 1 2 3 4 5 6 7 8 9 0 ° _
² & é " ' ( § è ! ç à ) -
A Z E R T Y U I O P ¨ *
a z e r t y u i o p ^ $
Q S D F G H J K L M % £
q s d f g h j k l m ù µ

Post by Kiem Lam
W X C V B N ? . / +

< w x c v b n , ; : =

AltGr is the key immediately to the right of the space bar (symmetrical
to the Alt key).

Here are AltGr combinations and dead keys, in keyboard geographical
sequence:

AltGr+& gives | (bar)
AltGr+é gives @ (atsign)
AltGr+" gives # (crosshatch)
AltGr+' gives { (opening brace; synonym of AltGr+ç)
AltGr+( gives [ (left bracket; synonym of AltGr+$)
AltGr+§ gives ^ (spacing circumflex; synonym of ^+space)
AltGr+ç gives { (opening brace)
AltGr+à gives } (closing brace)
AltGr+e gives € (euro sign)
¨ is dead key, followed by any vowel adds umlaut/diaeresis
followed by space, gives ¨ (spacing diaeresis)
^ is dead key, followed by any vowel adds circumflex
followed by space, gives ^ (spacing circumflex)
AltGr+^ gives [ (left bracket)
AltGr+$ gives ] (right bracket)
AltGr+ù is dead key, followed by any vowel adds acute accent
followed by space, gives ´ (spacing acute accent)
AltGr+µ is dead key, followed by any vowel adds grave accent
followed by space, gives ` (spacing grave accent)
AltGr+< gives \ (backslash)
AltGr+= is dead key, followed by a o n adds tilde
followed by space, gives ~ (spacing tilde)

That's all, AFAICT.

Best regards,
Tony.

Benji Fisher

2006-02-13 14:51:11 UTC

Permalink

Post by Kiem Lam

Post by A. J. Mechelynck

I have a Belgian keyboard (fr_BE to be precise) and I have no problems
with it, neither in Vim nor in gvim.
1. Do you change the 'encoding' option somewhere (e.g., in your
vimrc)? If you do, try saving its value in 'termencoding', for
if &termencoding == ""
let &termencoding = &encoding
endif
set encoding=utf8
" etc.
2. Does it happen that you change the keyboard setting and/or language
using non-Vim OS tools ("International keyboard" widget et al.)? If it
does, especially while Vim is running, Vim (or gvim) is not aware of the
change and endless problems can happen.
3. "Normally" anything keyboard-related should by default work
identically in Insert/Replace and Command-line mode... unless you have
mappings for the one which do not affect the other. This brings a third
Do you have cmap or imap (but not both) for some alt-keys (known in
mappings as <A- something > or <M- something >? Some Alt-keys are
indistinguishable to (g)vim from some accented characters from the
second half of the 8-bit ASCII set. Some of those accented characters
are obtained on the Belgian keyboard by Alt-Gr+something followed by
something (e.g., Alt-Gr+ù followed by E for capital-E-acute).

Hello,
First of all, thanks for your answer.
1. I do not change the "encoding" option anywhere.
2. So far, I do not think that I change the keyboard setting anywhere.
3. I checked my mappings but I do not think that the problem is coming
vim -N -u NONE
gvim -N -u NONE
I exactly have the same behavior. It works perfectly in vim and I am
encoutering the same problems as the ones described in my previous
email in gvim.
Fo information, previously, I was using vim (and gvim) 5.7 in the same
environment and everything was working fine.

Hello,
I am still struggling my "Alt Gr" key in Gvim ;-( (belgian keyboard).
As explained in my previous emails, it does not work in Insert mode
and in the search pattern command (/string), but it works in the
command mode (:command). Moreover, it works just fine in vim.
If anybody could help me out, it would be greatly appreciated!
Regards,
Kiem

First, please do not reply at the top after someone has already
replied at the bottom (or vice-versa). This makes the exchange very
hard to read. If you feel strongly about bottom- or top-replying, and
are adding to a thread that already has the other sort of reply, please
take the trouble to edit what you are quoting so that it is in the same
format.

This is hard for me to help with, since I have neither the right
system (HP-UX) nor the right keyboard, but I will see what I can do.
Let me start with some questions.

1. Do you see the problem when using the same binary? Start with vim in
a terminal, test it, and then start the GUI:

$ vim
<Do some editing>
:gui
<Do some editing>

While you are at it, check the values of the encoding options in both
terminal and GUI.

:verbose set enc? tenc? fenc?

2. What is the :version output? One way to get it:

:redir @a
:version
:redir END
:put a

3. What happens, in terminal and the GUI, when you enter text in
creative ways? Replace "@" with some character that you enter with the
Alt-Gr key:

a. (Insert mode) @ (not creative)
b. (Insert mode) <C-V>@
c. (Insert mode) <C-R>='@'<CR>
d. :put='@'

If you are not sure of the results, use "ga" or "g8" (in Normal mode) to
figure out what character is under the cursor.

:help ga

HTH --Benji Fisher

Kiem Lam

2006-02-14 01:49:18 UTC

Permalink

Post by Benji Fisher

Post by Kiem Lam

Post by A. J. Mechelynck

Hello,
I am still struggling my "Alt Gr" key in Gvim ;-( (belgian keyboard).
As explained in my previous emails, it does not work in Insert mode
and in the search pattern command (/string), but it works in the
command mode (:command). Moreover, it works just fine in vim.
If anybody could help me out, it would be greatly appreciated!
Regards,
Kiem

First, please do not reply at the top after someone has already
replied at the bottom (or vice-versa). This makes the exchange very
hard to read. If you feel strongly about bottom- or top-replying, and
are adding to a thread that already has the other sort of reply, please
take the trouble to edit what you are quoting so that it is in the same
format.
This is hard for me to help with, since I have neither the right
system (HP-UX) nor the right keyboard, but I will see what I can do.
Let me start with some questions.
1. Do you see the problem when using the same binary? Start with vim in
$ vim
<Do some editing>
:gui
<Do some editing>
While you are at it, check the values of the encoding options in both
terminal and GUI.
:verbose set enc? tenc? fenc?
:version
:redir END
:put a
3. What happens, in terminal and the GUI, when you enter text in
If you are not sure of the results, use "ga" or "g8" (in Normal mode) to
figure out what character is under the cursor.
:help ga
HTH --Benji Fisher

Hello Benji,

Sorry about my reply's layout. I'll be careful about it from now on.

Here are the tests' results:

1. Text editing (Insert mode):

- No problem under vim.
- Under gvim, instead of "|@#\" (between double-quote), I get "&é"'"
(between double-quote)(actually, I do not get "é" but I get a capital
"A" with a circle on the top of it - a Scandinavian character, I
think- however I am not able to reproduce it in this email).
- The commands :verbose set enc? always replies "E519: Option not
supported: enc?". Same goes for tenc? and fenc?.

2. Version:

VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Feb 8 2006 14:42:56)
Compiled by ***@mcrs2
Normal version with GTK GUI. Features included (+) or not (-):
-arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +cryptv -cscope +dialog_con_gui +diff
+digraphs +dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search
-farsi
+file_in_path +find_in_path +folding -footer +fork() -gettext
-hangul_input -iconv +insert_expand +jumplist -keymap -langmap
+libcall
+linebreak +lispindent +listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape -mouse_dec -mouse_gpm -mouse_jsbterm
-mouse_netterm +mouse_xterm -multi_byte +multi_lang +netbeans_intg
-osfiletype +path_extra -perl +postscript +printer -python +quickfix
-rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline
-sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl
+terminfo +termresponse +textobjects +title +toolbar +user_commands
+vertsplit +virtualedit +visual +visualextra +viminfo +vreplace
+wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim
+xsmp_interact +xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/tcs_usr/kla/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/opt/gnome/include/gtk-1.2 -I/opt/gnome/include/glib-1.2
-I/opt/gnome/lib/glib/include -O2 -fno-strength-reduce -Wall
Linking: gcc -o vim -L/opt/gnome/lib -lgtk -lgdk -lgmodule -lglib
-lintl -lXext -lm -lICE -lXt -lncurses

3. Text editing in creative ways (command // vim display // gvim display):

- (Insert mode) @ (not creative) // @ // capital "A" with a circle on
the top of it
- (Insert mode) <C-V>@ // @ // capital "A" with a circle on the top of it
- (Insert mode) <C-R>='@'<CR> // @ // capital "A" with a circle on the top of it
- :put='@' // @ // @ (this one actually works)

Here is what I get with the "ga" command:
- "@" -----> <@> 64, Hex 40, Octal 100
- "A" with circle -----> <é> <|E> <M-E> 197, Hex c5, Octal 305
(please read "A" with circle instead of "é")

That's it. Hope this feedback will give you any hint about what my problem is.

Regards,
--
Kiem Lam

A. J. Mechelynck

2006-02-14 02:24:36 UTC

Permalink

Kiem Lam wrote:
[...]

Post by Kiem Lam
(between double-quote)(actually, I do not get "é" but I get a capital
"A" with a circle on the top of it - a Scandinavian character, I
think- however I am not able to reproduce it in this email).
- The commands :verbose set enc? always replies "E519: Option not
supported: enc?". Same goes for tenc? and fenc?.

[...]

Post by Kiem Lam
-mouse_netterm +mouse_xterm -multi_byte +multi_lang +netbeans_intg

[...]

"-multi_byte" is the reason why 'enc' 'tenc' and 'fenc' are unsupported.

I could be wrong, but it sounds like your X11 GUI interface and your
console terminal don't send the same keyboard codes, and Vim understands
the one but not the other. Different charsets in the terminal and in the
GUI keyboard isn't something uncommon: for instance, IIUC, my Windows
applications (such as gvim) get their keystrokes in Windows-1252
encoding but my "Dos box" applications (such as console Vim) get theirs
in cp437.

If I were you I'd try to lay hands on a version with +multi_byte (or
possibly +multi_byte_ime or +multi_byte_ime/dyn, which include it). That
feature is not only useful for encodings actually supporting more than
one byte per character (like Unicode, or anything used for Chinese,
Japanese or Korean), but also for translating between different 8-bit
character sets (especially if it has +iconv with or without /dyn). It is
essential if your version of X11 sends keystrokes in Unicode.

If you compile gvim yourself, try --with-features=big (or
--with-features=huge but AFAIK the only difference between them is the
"profiling" feature).

Best regards,
Tony.

Benji Fisher

2006-02-14 04:03:57 UTC

Permalink

Post by A. J. Mechelynck
[...]

Post by Kiem Lam
-mouse_netterm +mouse_xterm -multi_byte +multi_lang +netbeans_intg

[...]
"-multi_byte" is the reason why 'enc' 'tenc' and 'fenc' are unsupported.

That is what I was thinking.

Post by A. J. Mechelynck
If you compile gvim yourself, try --with-features=big (or
--with-features=huge but AFAIK the only difference between them is the
"profiling" feature).

I second that suggestion. I am also curious about the :version
output from vim 5.7, which did not give such trouble.

HTH --Benji Fisher

Kiem Lam

2006-02-14 07:03:18 UTC

Permalink

Post by Benji Fisher

Post by A. J. Mechelynck
[...]

Post by Kiem Lam
-mouse_netterm +mouse_xterm -multi_byte +multi_lang +netbeans_intg

[...]
"-multi_byte" is the reason why 'enc' 'tenc' and 'fenc' are unsupported.

That is what I was thinking.

Post by A. J. Mechelynck
If you compile gvim yourself, try --with-features=big (or
--with-features=huge but AFAIK the only difference between them is the
"profiling" feature).

I second that suggestion. I am also curious about the :version
output from vim 5.7, which did not give such trouble.
HTH --Benji Fisher

Hello,

I recompiled vim with --with-features=big. I am still facing the same
problem :-(. Here is what I get for the version:

VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Feb 14 2006 15:28:45)
Compiled by ***@mcrs2
Big version with GTK GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +cryptv +cscope +dialog_con_gui +diff
+digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
+farsi
+file_in_path +find_in_path +folding -footer +fork() -gettext
-hangul_input +iconv +insert_expand +jumplist +keymap +langmap
+libcall
+linebreak +lispindent +listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm
+mouse_netterm +mouse_xterm +multi_byte +multi_lang +netbeans_intg
-osfiletype +path_extra -perl +postscript +printer -python +quickfix
+rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline
-sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl
+terminfo +termresponse +textobjects +title +toolbar +user_commands
+vertsplit +virtualedit +visual +visualextra +viminfo +vreplace
+wildignore +wildmenu +windows +writebackup +X11 +xfontset +xim
+xsmp_interact +xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/tcs_usr/kla/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/opt/gnome/include/gtk-1.2 -I/opt/gnome/include/glib-1.2
-I/opt/gnome/lib/glib/include -g -O2
Linking: gcc -o vim -L/opt/gnome/lib -lgtk -lgdk -lgmodule -lglib
-lintl -lXext -lm -lICE -lXt -lncurses

I am now able to run the :verbose set enc? command and it returns
encoding=latin1. I tried :set enc=utf-8 but there was no improvement
(I got a capital "A" with a "~" on the top of it instead of the
circle... Ô joie! Ô allégresse!).

For comparison purpose, I ran vim 5.7 and I printed out its version.
Here is what I got:

VIM - Vi IMproved 5.7 (2000 Jun 24, compiled Nov 14 2000 10:11:45)
Compiled with (+) or without (-):
+autocmd +browse +builtin_terms +byte_offset +cindent +cmdline_compl
+cmdline_info +comments +cryptv -cscope +dialog_con_gui +digraphs
-emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path
-osfiletype +find_in_path +fork() +GUI_Motif
-hangul_input +insert_expand -langmap +linebreak +lispindent +menu
+mksession +modify_fname +mouse -mouse_dec -mouse_gpm
-mouse_netterm +mouse_xterm -multi_byte -perl -python +quickfix
-rightleft +scrollbind +smartindent -sniff +statusline
+syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo
+textobjects +title +user_commands +visualextra +viminfo
+wildignore +wildmenu +writebackup +X11 -xfontset -xim
+xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DUSE_GUI_MOTIF -I.
-g -O2 -Wall
Linking: gcc -o vim -L. -lXext -lXm -lXp -lXt -lXt -lX11 -ltermlib

Can the source of my problem lie in the difference between some
compilation options? I looked at them but I am not very familiar with
them.

Regards,
--
Kiem Lam

Benji Fisher

2006-02-14 15:13:14 UTC

Permalink

Post by Kiem Lam
Hello,
I recompiled vim with --with-features=big. I am still facing the same
VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Feb 14 2006 15:28:45)

^^^^^^^
[snip]

Post by Kiem Lam
VIM - Vi IMproved 5.7 (2000 Jun 24, compiled Nov 14 2000 10:11:45)
+autocmd +browse +builtin_terms +byte_offset +cindent +cmdline_compl
+cmdline_info +comments +cryptv -cscope +dialog_con_gui +digraphs
-emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path
-osfiletype +find_in_path +fork() +GUI_Motif

^^^^^^^^^^
[snip]

So my next suggestion is to re-compile with the Motif GUI instead of
GTK. From the src/ directory, either

$ ./configure --enable-gui=motif
$ make

or edit src/Makefile to un-comment the lines

#CONF_OPT_GUI = --disable-gtk-check
#CONF_OPT_GUI = --disable-gtk2-check

and then

$ make reconfig

While you are at it, it might be a good idea to search src/Makefile for
"HP-UX" and un-comment some of the recommended lines. Keep your fingers
crossed ...

HTH --Benji Fisher

Kiem Lam

2006-02-16 00:52:15 UTC

Permalink

Hello,

I re-compiled with the Motif GUI instead of the GTK GUI and IT WORKS!

I would like to thank you all for your great help (and your patience).

Regards,

Kiêm

Post by Benji Fisher

Post by Kiem Lam
Hello,
I recompiled vim with --with-features=big. I am still facing the same
VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Feb 14 2006 15:28:45)

^^^^^^^
[snip]

^^^^^^^^^^
[snip]
So my next suggestion is to re-compile with the Motif GUI instead of
GTK. From the src/ directory, either
$ ./configure --enable-gui=motif
$ make
or edit src/Makefile to un-comment the lines
#CONF_OPT_GUI = --disable-gtk-check
#CONF_OPT_GUI = --disable-gtk2-check
and then
$ make reconfig
While you are at it, it might be a good idea to search src/Makefile for
"HP-UX" and un-comment some of the recommended lines. Keep your fingers
crossed ...
HTH --Benji Fisher

--
Kiem Lam