On Thursday 02 August 2001 13:02, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | On Thursday 02 August 2001 12:19, Lars Gullik Bjønnes wrote:
> | > Angus Leeming <[EMAIL PROTECTED]> writes:
> | >
> | > | When I press my compose key I get the minibuffer message "unknown
> | function"
> | > | and I can't create accented chars. Things work fine in other apps, so
> | this
> | > | appears to be a LyX problem not an X one.
> | > |
> | > | Do other people see this?
> | >
> | > If you turn on debugging... what does LyX think it sees?
> |
> | compose+e+' and LyX thinks that it sees eacute. The display however goes
> | compose nothing
> | e e
> | ' e'
>
> and eacute is not working... bind file problem?
Why would I be using a bind file for this? Surely, eacute is used to create
the appropriate insetspecialchar using the cdef files.
Anyway, this is not a local bind files problem. All my installed bind files
are identical to those in HEAD.
Things work this way whether or not I have set the preferences option
"Override X dead keys".
What else do I have to alter? Do things work as they should for other people?
Things still seem wrong to me. If I hit the compose key, then the next two
characters I hit should not be drawn on screen at all, only the translated
character. (Ie, they should not be drawn on screen as e' and then translated
to é.) At least, that's how other packages (kde stuff, emacs) does it.
Angus
