From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: find-function-C-source-directory
Date: Mon, 29 May 2006 06:33:57 +0300 [thread overview]
Message-ID: <u1wudh5cq.fsf@gnu.org> (raw)
In-Reply-To: <447A222B.6030804@student.lu.se> (message from Lennart Borgman on Mon, 29 May 2006 00:20:27 +0200)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
> Date: Mon, 29 May 2006 00:20:27 +0200
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> CC: emacs-devel@gnu.org
>
> Eli Zaretskii wrote:
> >> Sorry, I misread Eli´s answer. I mean that they have no way to find out
> >> that they should set find-function-C-source-directory if they want Emacs
> >> to know permanently where the C sources are.
> >>
> >
> > You mean, for the other sessions as well? Because for this session,
> > Emacs remembers the place, and never prompts again.
> >
> Yes, that is what I mean.
Do we have a reason to believe that the sources will be in the same
place for the next session? My Emacs sessions end only when the
system goes down (which happens once in a blue moon). If the user
brings the sources from outside, she might as well change the location
in between.
next prev parent reply other threads:[~2006-05-29 3:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 21:50 find-function-C-source-directory Lennart Borgman
2006-05-28 3:05 ` find-function-C-source-directory Eli Zaretskii
2006-05-28 9:22 ` find-function-C-source-directory Lennart Borgman
2006-05-28 18:19 ` find-function-C-source-directory Richard Stallman
2006-05-28 19:07 ` find-function-C-source-directory Lennart Borgman
2006-05-28 20:26 ` find-function-C-source-directory Eli Zaretskii
2006-05-28 22:20 ` find-function-C-source-directory Lennart Borgman
2006-05-29 3:33 ` Eli Zaretskii [this message]
2006-05-29 5:37 ` find-function-C-source-directory Lennart Borgman
2006-05-28 3:18 ` find-function-C-source-directory 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=u1wudh5cq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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 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).