unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
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: Sun, 20 Oct 2002 15:52:49 -0400	[thread overview]
Message-ID: <200210201952.g9KJqnx12700@rum.cs.yale.edu> (raw)
In-Reply-To: E183JQR-0005QH-00@fencepost.gnu.org

>     I have enhanced the Emacs `compile' package with some commands.
> 
>     1. Automatic selection of compile commands according to the file
>        extension and DEBUG state. (defuns: `compile-main', `compile-sub',
>        `compile-debug-toggle')
> 
> The debugging feature could make sense, but why isn't `make -k' a good
> default regardless of the kind of file?  In other words, why isn't
> "You should write a proper makefile" a good solution for this?

I have missed the orinal post, where was it ?
[ was it in gnu.emacs.bug ?  My gnu.emacs.bug newsgroup has been empty
  for a while now. ]

>     4. An easy way to interact (send input to) with the compilation process
>        (`compile-send-to-process').
> 
> This indeed is something important.
> 
> 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))


	Stefan

  parent reply	other threads:[~2002-10-20 19:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <iPgs9.26259$wU3.2299106@news0.telusplanet.net>
     [not found] ` <200210200000.g9K00B5d021923@beta.mvs.co.il>
2002-10-20 16:59   ` M-x compile for different file extensions 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 [this message]
2002-10-20 22:05       ` Ehud Karni
2002-10-22  3:12       ` Richard Stallman

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=200210201952.g9KJqnx12700@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --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 public inbox

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

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).