From: vose <vose@cs.utk.edu>
Subject: Re: example .emacs file
Date: Fri, 22 Aug 2003 14:22:27 -0400 [thread overview]
Message-ID: <3f4660ba_1@news.utk.edu> (raw)
In-Reply-To: <3f465a20$1_1@news.utk.edu>
vose wrote:
> I have GNU Emacs 20.7.1 (i386-redhat-linux-gnu, X toolkit).
>
> If anyone has this same version and also has a .emacs file
> which manages to make function keys do something useful in
> tex mode --- like, for example, when the "F1" function key
> followed by the "b" key is pushed, the result is that some
> character string (like "\begin", for example) is inserted
> into the buffer after the point, assuming emacs has been
> started from an xterm --- PLEASE mail me the .emacs file.
>
> Absolutely NOTHING I have tried (including cutting and pasting
> from FAQs) works.
>
> Michael
>
The .emacs file shipped to me by redhat with their enterprise
edition contains errors which cause later s-expressions (the
ones which should have successfully dealt with function keys)
to be ingored. I just discovered this bug. Things are looking
up.
Michael
prev parent reply other threads:[~2003-08-22 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 17:54 example .emacs file vose
2003-08-22 18:22 ` vose [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f4660ba_1@news.utk.edu \
--to=vose@cs.utk.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).