From: "Suttles, Andrew C. (GRC-DSI0)" <andrew.c.suttles@nasa.gov>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Using only one emacs session
Date: Mon, 18 May 2009 08:14:30 -0500 [thread overview]
Message-ID: <9A19D3881CEC5941A7AE5A097554E8414C16ECE2F6@NDJSSCC05.ndc.nasa.gov> (raw)
In-Reply-To: <92e05b99-6fe0-4092-bedf-9fa64a883422@g19g2000vbi.googlegroups.com>
Good point. I was thinking of two small programming projects where I am the chief code maintainer. However, if the only local variable at the bottom of the source is "compile-command", it seems to be a good solution. The compile command should be the same for whoever edits the source for projects with simple compile commands.
>-----Original Message-----
>From: help-gnu-emacs-bounces+andrew.c.suttles=nasa.gov@gnu.org
>[mailto:help-gnu-emacs-bounces+andrew.c.suttles=nasa.gov@gnu.org] On
>Behalf Of Francis Moreau
>Sent: Saturday, May 16, 2009 8:33 AM
>To: help-gnu-emacs@gnu.org
>Subject: Re: Using only one emacs session
>
>On May 15, 6:50 pm, "Suttles, Andrew C. (GRC-DSI0)"
><andrew.c.sutt...@nasa.gov> wrote:
>> I put local variables at the bottom of each project file I write code
>in. When I load the source files, the compile command is automatically
>configured.
>>
>
>
>IMHO, that's not a good solution because if you work on project with
>several people, each person can't clutter each file with his editor
>configuration. And if you want to change one value of a variable you
>need to edit all files of the project.
next prev parent reply other threads:[~2009-05-18 13:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 11:04 Using only one emacs session Francis Moreau
2009-05-15 11:47 ` Peter Dyballa
2009-05-15 12:48 ` Pascal J. Bourguignon
2009-05-15 13:34 ` Francis Moreau
[not found] ` <mailman.7199.1242388057.31690.help-gnu-emacs@gnu.org>
2009-05-15 12:50 ` Pascal J. Bourguignon
2009-05-15 12:53 ` Francis Moreau
2009-05-15 13:36 ` Pascal J. Bourguignon
2009-05-15 13:45 ` Francis Moreau
2009-05-15 14:55 ` Peter Dyballa
2009-05-15 16:50 ` Suttles, Andrew C. (GRC-DSI0)
[not found] ` <mailman.7245.1242439486.31690.help-gnu-emacs@gnu.org>
2009-05-16 12:33 ` Francis Moreau
2009-05-18 13:14 ` Suttles, Andrew C. (GRC-DSI0) [this message]
[not found] ` <mailman.7205.1242399319.31690.help-gnu-emacs@gnu.org>
2009-05-15 16:02 ` Francis Moreau
2009-05-15 21:41 ` Pascal J. Bourguignon
2009-05-15 14:13 ` Michael Ekstrand
2009-05-15 14:38 ` Peter Dyballa
2009-05-16 11:14 ` Vagn Johansen
2009-05-15 13:38 ` Lowell Gilbert
2009-05-15 14:00 ` tomas
[not found] ` <mailman.7201.1242394726.31690.help-gnu-emacs@gnu.org>
2009-05-15 13:49 ` Francis Moreau
2009-05-15 17:07 ` William Xu
[not found] ` <mailman.7216.1242408514.31690.help-gnu-emacs@gnu.org>
2009-05-16 12:55 ` Francis Moreau
2009-05-16 15:43 ` Pascal J. Bourguignon
2009-05-16 21:53 ` Francis Moreau
2009-05-16 23:05 ` Pascal J. Bourguignon
2009-05-17 7:01 ` Francis Moreau
2009-05-17 15:32 ` Pascal J. Bourguignon
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=9A19D3881CEC5941A7AE5A097554E8414C16ECE2F6@NDJSSCC05.ndc.nasa.gov \
--to=andrew.c.suttles@nasa.gov \
--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.
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.