From: Ed L Cashin <ecashin@uga.edu>
Subject: Re: customize messing up .emacs symlink?
Date: Tue, 02 Mar 2004 13:06:46 -0500 [thread overview]
Message-ID: <87vflnw2bt.fsf@cs.uga.edu> (raw)
In-Reply-To: pan.2004.03.02.15.36.15.78369@dzr-web.com
"D. D. Brierton" <darren@dzr-web.com> writes:
...
> Ahhh. I'd misunderstood you. I thought you meant that you were running two
> different emacsen on the same box, but rather the problem seems to be with
> two identical emacsen on different boxes.
Re-reading my original post, I now realize that I was not at all clear
about that. I use svn to keep track of some files that are the same
across all the machines I use. My .emacs file is one such file.
>> To me it seems wrong for the default behavior of customize to be like
>> this, replacing a symlinked .emacs file with a modified regular file.
>
> Yes, I'd agree, although I suppose it depends on what the symlink is to --
> is it something very exotic, like a pointer via a virtual-file-system
> directly into your version constrol repository? (Perhaps that's not
> possible. Perhaps it is possible and not at all exotic.)
No, it points to a regular file in a working copy of a directory in
the repository.
>> Does anyone know if this feature has been discussed to death already,
>> or would it be good to submit a bug report?
>
> I haven't seen it mentioned before, and I lurk here a lot, and regular
> browse the web archive of the developers' list.
I'd say it's a bug, but it's kind of a trivial matter, and if it isn't
bothering others, I'll just work around it.
>>> But assuming its Xemacs vs.
>>> Emacs, put at the end of your .emacs something like (excuse my probably
>>> crappy and very-unlisp-like lisp):
>>>
>>> (if (string-match "XEmacs" emacs-version)
>>> (load "~/.xemacs.customize.el")
>>> (load "~/.emacs.customize.el"))
>>
>> Looks like a good solution for me.
Something even more simple is the .emacs file below, a regular file on
both machines, changable by customize without problem:
;;;; .emacs
(load "~/svnfiles/homedir/.emacs")
--
--Ed L Cashin PGP public key: http://noserose.net/e/pgp/
next prev parent reply other threads:[~2004-03-02 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 2:00 customize messing up .emacs symlink? Ed L Cashin
2004-03-02 4:03 ` D. D. Brierton
2004-03-02 15:09 ` Ed L Cashin
2004-03-02 15:36 ` D. D. Brierton
2004-03-02 18:06 ` Ed L Cashin [this message]
2004-03-02 16:24 ` Floyd L. Davidson
2004-03-03 0:55 ` Ed L Cashin
2004-03-03 1:02 ` Jesper Harder
2004-03-02 18:52 ` Kevin Rodgers
2004-03-03 0:59 ` Ed L Cashin
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=87vflnw2bt.fsf@cs.uga.edu \
--to=ecashin@uga.edu \
/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).