From: Chong Yidong <cyd@stupidchicken.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "T.V. Raman" <tv.raman.tv@gmail.com>,
Dan Nicolaescu <dann@ics.uci.edu>,
emacs-devel@gnu.org
Subject: Re: files.el: Patch to make project-settings optional/customizable
Date: Thu, 13 Nov 2008 12:14:22 -0500 [thread overview]
Message-ID: <87prkz4kgh.fsf@cyd.mit.edu> (raw)
In-Reply-To: <m3prkz8tir.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 13 Nov 2008 09:45:00 -0700")
Tom Tromey <tromey@redhat.com> writes:
> Dan> If no, what is the advantage of having this name customizable?
> Dan> What happens if different projects using different names?
> Dan> It seems that it would just bring in complications...
>
> Yes, this makes the feature less useful, by making it not work
> automatically across projects.
I think it's generally good policy to avoid hardcoding file names. The
default is unchanged, so the feature still works automatically across
projects unless you change it. People who care enough about changing
the default presumably know what they are doing (presumably, they want
to have a different file name for some reasons of their own, and this
change lets them do that without redefining the functions).
next prev parent reply other threads:[~2008-11-13 17:14 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 14:29 files.el: Patch to make project-settings optional/customizable T.V. Raman
2008-11-13 15:20 ` Chong Yidong
2008-11-13 16:07 ` Dan Nicolaescu
2008-11-13 16:19 ` Dan Nicolaescu
2008-11-13 16:45 ` Tom Tromey
2008-11-13 17:14 ` Chong Yidong [this message]
2008-11-13 17:28 ` Dan Nicolaescu
2008-11-13 17:55 ` Juanma Barranquero
2008-11-13 17:59 ` Dan Nicolaescu
2008-11-13 19:13 ` Juanma Barranquero
2008-11-13 19:00 ` Tom Tromey
2008-11-13 19:15 ` Juanma Barranquero
2008-11-13 18:26 ` Chong Yidong
2008-11-13 18:48 ` Dan Nicolaescu
2008-11-18 16:36 ` Dan Nicolaescu
2008-11-18 22:04 ` Juri Linkov
2008-11-18 22:15 ` Dan Nicolaescu
2008-11-18 22:42 ` Juanma Barranquero
2008-11-18 23:18 ` Dan Nicolaescu
2008-11-18 23:41 ` Juanma Barranquero
2008-11-18 22:59 ` Stefan Monnier
2008-11-18 23:31 ` Juri Linkov
2008-11-18 23:33 ` Chong Yidong
2008-11-18 23:41 ` Dan Nicolaescu
2008-11-18 23:50 ` Juanma Barranquero
2008-11-19 0:14 ` Dan Nicolaescu
2008-11-19 1:48 ` Chong Yidong
2008-11-19 8:26 ` Juanma Barranquero
2008-11-19 12:52 ` Richard M. Stallman
2008-11-18 23:37 ` Juanma Barranquero
2008-11-19 2:01 ` Stefan Monnier
2008-11-19 8:39 ` Juanma Barranquero
2008-11-19 13:27 ` Dan Nicolaescu
2008-11-19 22:45 ` Juri Linkov
2008-11-19 22:58 ` Tom Tromey
2008-11-20 2:18 ` Stefan Monnier
2008-11-22 19:08 ` Juri Linkov
2008-11-22 19:40 ` Dan Nicolaescu
2008-11-22 19:51 ` Juri Linkov
2008-11-22 20:20 ` Dan Nicolaescu
2008-11-22 22:03 ` Juanma Barranquero
2008-11-23 3:34 ` Miles Bader
2008-11-23 5:27 ` Stefan Monnier
2008-11-23 5:36 ` Juanma Barranquero
2008-11-23 5:58 ` Stefan Monnier
2008-11-23 8:10 ` Dan Nicolaescu
2008-11-23 10:45 ` Juri Linkov
2008-11-23 12:10 ` Dan Nicolaescu
2008-11-23 12:41 ` Juanma Barranquero
2008-11-23 17:16 ` Dan Nicolaescu
2008-11-23 17:45 ` Juanma Barranquero
2008-11-23 21:21 ` Dan Nicolaescu
2008-11-24 2:14 ` Stephen J. Turnbull
2008-11-24 3:06 ` Dan Nicolaescu
2008-11-24 5:35 ` Chong Yidong
2008-11-22 4:03 ` Kevin Rodgers
2008-11-19 4:07 ` Stephen J. Turnbull
2008-11-13 19:04 ` Tom Tromey
2008-11-13 19:23 ` Tom Tromey
2008-11-13 19:55 ` Juanma Barranquero
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=87prkz4kgh.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=tromey@redhat.com \
--cc=tv.raman.tv@gmail.com \
/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.