all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: ehud@unix.mvs.co.il, wgh@askme.ok, henrik+news@enberg.org,
	emacs-devel@gnu.org
Subject: Re: M-x compile for different file extensions
Date: Mon, 21 Oct 2002 23:12:44 -0400	[thread overview]
Message-ID: <E183pTI-0000Od-00@fencepost.gnu.org> (raw)
In-Reply-To: <200210201952.g9KJqnx12700@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

    > It is sort of unfortunate that we have the conflict between two
    > meanings we would like RET to have in the compilation buffer: "visit
    > the source code for a particular error message", and "send a line of
    > input".  We have used it for the former ever since that convention
    > existed in Emacs (several years ago), but would it be better to use
    > it for the latter instead?

    We could probably let RET do something like
    (if (eobp) (send-to-process) (goto-error))

This is a good solution if users prefer it.

  parent reply	other threads:[~2002-10-22  3:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19 17:41 M-x compile for different file extensions wgh
2002-10-19 18:23 ` Henrik Enberg
2002-10-20  0:00 ` Ehud Karni
2002-10-20 16:59   ` Richard Stallman
2002-10-20 18:07     ` Ehud Karni
2002-10-20 19:51       ` Stefan Monnier
2002-10-22  3:12       ` Richard Stallman
2002-10-22  6:46         ` Kai Großjohann
2002-10-22 17:17           ` Kevin Rodgers
2002-10-22 19:03             ` Ehud Karni
2002-10-23  7:11           ` Richard Stallman
2002-10-22 18:23         ` Ehud Karni
2002-10-23  7:10           ` Richard Stallman
2002-10-20 19:52     ` Stefan Monnier
2002-10-20 22:05       ` Ehud Karni
2002-10-22  3:12       ` Richard Stallman [this message]
2002-10-21 18:40 ` kgold
2002-10-22  5:33   ` James Cozine

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E183pTI-0000Od-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=ehud@unix.mvs.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=henrik+news@enberg.org \
    --cc=wgh@askme.ok \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.