unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: duke <sidney.reilley.ii@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Passing current buffer to compile command
Date: Sun, 16 Jan 2011 17:29:14 -0800 (PST)	[thread overview]
Message-ID: <91cb958b-a130-4dcf-99b9-7ee2ddf710a7@15g2000vbz.googlegroups.com> (raw)
In-Reply-To: mailman.1.1295218445.29897.help-gnu-emacs@gnu.org

On Jan 16, 3:53 pm, Eli Zaretskii <e...@gnu.org> wrote:
> > From: duke <sidney.reilley...@gmail.com>
> > Newsgroups: gnu.emacs.help
> > Date: Sun, 16 Jan 2011 13:54:26 -0800 (PST)
>
> > I do M-x compile  or goto the menu M-` t c
> > then I'm in the mini-buffer.
> > I enter my compiler name; I've always typed-in the filename currently
> > being edited.
> > I'm wondering if there's another to pass that filename to the mini-
> > buffer?
>
> Customize the value of compile-command.  You can put it in the file's
> local variables section for each file that you edit.

This is not Lisp, or even elisp that I'm coding in. Does that matter
with
respect to the "local variables" you mention above? I tried what was
suggested in another post concerning "local variables". Didn't work -
or I'm not doing it correctly. :)

> > I realize that once I have a compiling history for the session, I can
> > navigate using the arrows, but it's that first time that I'm exploring.
>
> Even better: use "M-x recompile" after the first time, it will reissue
> the same command automatically.

Excellent! Thanks ...


  parent reply	other threads:[~2011-01-17  1:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 19:12 Passing current buffer to compile command duke
2011-01-16 20:50 ` Peter Dyballa
2011-01-16 21:12 ` Pascal J. Bourguignon
     [not found] ` <mailman.12.1295211063.24679.help-gnu-emacs@gnu.org>
2011-01-16 21:54   ` duke
2011-01-16 22:53     ` Eli Zaretskii
2011-01-19  4:41       ` Kevin Rodgers
2011-01-16 23:42     ` Peter Dyballa
     [not found]     ` <mailman.1.1295218445.29897.help-gnu-emacs@gnu.org>
2011-01-17  1:29       ` duke [this message]
2011-01-17 12:44         ` Eli Zaretskii
     [not found]         ` <mailman.2.1295268672.1793.help-gnu-emacs@gnu.org>
2011-01-17 19:08           ` duke
2011-01-16 21:58 ` despen
2011-01-17  5:48   ` despen
2011-01-17 19:09     ` duke
2011-01-17  3:29 ` rusi
2011-01-17  3:49   ` rusi
2011-01-17 19:07     ` duke
2011-01-18  3:42       ` rusi
2011-01-18  4:05         ` rusi
2011-01-18 16:06           ` Le Wang
     [not found]           ` <mailman.0.1295366801.24998.help-gnu-emacs@gnu.org>
2011-01-19 20:12             ` duke
2011-01-18  5:14         ` duke
2011-01-21  1:08     ` Drew Adams

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=91cb958b-a130-4dcf-99b9-7ee2ddf710a7@15g2000vbz.googlegroups.com \
    --to=sidney.reilley.ii@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).