From: Kai Grossjohann <kai.grossjohann@gmx.net>
Subject: Re: Strange mini-buffer problem
Date: Wed, 01 Oct 2003 00:13:32 +0200 [thread overview]
Message-ID: <8665j9ylf7.fsf@slowfox.dyndns.org> (raw)
In-Reply-To: 3F681F6E.6010008@gmx.net
Thomas Heinz <thomasheinz@gmx.net> writes:
> I'm currently experiencing a strange problem which "suddenly" appeared.
> I'm using the auc tex mode and when I type C-c C-c a line in the mini buffer
> appears stating "Command: (default LaTex)". Usually, when I press return the
> command "latex <file>" is being executed.
>
> Now, after pressing return nothing happens. In fact, I need to enter the
> mini-buffer (menu->Minibuf->Enter) to let the command being executed.
> Of course, I don't want to do that every time I need to compile my document.
> Any ideas what made this happen?
Did you bind the <return> key? Don't do that. Do change the binding
of the return key, use
(global-set-key (kbd "RET") 'some-command)
; ^^^^^^^^^^^
; the important part
Just a stab in the dark.
Kai
prev parent reply other threads:[~2003-09-30 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 8:46 Strange mini-buffer problem Thomas Heinz
2003-09-30 22:13 ` Kai Grossjohann [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=8665j9ylf7.fsf@slowfox.dyndns.org \
--to=kai.grossjohann@gmx.net \
/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).