From: Dieter Wilhelm <dieter@duenenhof-wilhelm.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: current directory
Date: Mon, 23 Oct 2006 23:47:23 +0200 [thread overview]
Message-ID: <87ac3mu2l0.fsf@hans.local.net> (raw)
In-Reply-To: <200610231336.12203.help-gnu-emacs@vsbe.com> (vb's message of "Mon\, 23 Oct 2006 13\:36\:12 -0700")
vb <help-gnu-emacs@vsbe.com> writes:
> Let me ask you about another feature I am missing in emacs and which seems a
> bit more involved to implement myself: maintaining current setup over
> restarts. Say I quit emacs with several files open, each in its own window,
> at certain location in a file. Then I quit the session, do some other editing
> in a different directory tree, and then I come back to start emacs in the
> original directory. It comes up and shows me all those files in all those
> windows exactly the way they were when I quit the original editing session.
>
> Kind of a 'lightweight project management' feature - is it available?
Yes, of course, please have a look at "Saving Emacs Sessions" in the
GNU Emacs Manual. But I do not use these features myself. OK, at
first I was also thinking: Why the heck is there nothing like
"recently opened files" etc. in Emacs. But after a while I used Emacs
in another more efficient way. I just never close Emacs and opened
files between reboots.
>
> Guys, I really appreciate everybody's comments and replies. Sometimes when
> there is a newcomer bitching about the list topic the tensions get quite high
> - it's good to see that here we can have a dialog even though I am not quite
> completely charmed by emacs :-)
That is OK, otherwise the list wouldn't have the fun to convert an
unbeliever ;-).
--
Best wishes
H. Dieter Wilhelm
Darmstadt, Germany
next prev parent reply other threads:[~2006-10-23 21:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.83.1161235004.2130.help-gnu-emacs@gnu.org>
2006-10-19 16:01 ` current directory Fang lun gang
2006-10-19 16:52 ` vb
2006-10-20 6:22 ` Eli Zaretskii
[not found] ` <mailman.100.1161276782.2130.help-gnu-emacs@gnu.org>
2006-10-19 19:22 ` rgb
2006-10-19 21:00 ` vb
2006-10-21 18:38 ` don provan
2006-10-23 17:24 ` vb
2006-10-23 19:17 ` John Sullivan
2006-10-23 19:57 ` Eli Zaretskii
2006-10-23 20:36 ` vb
2006-10-23 21:47 ` Dieter Wilhelm [this message]
2006-10-24 4:26 ` Eli Zaretskii
2006-10-24 5:24 ` Dieter Wilhelm
[not found] ` <mailman.178.1161635783.27805.help-gnu-emacs@gnu.org>
2006-10-23 21:52 ` Maarten Bergvelt
2006-10-23 20:32 ` Kevin Rodgers
2006-10-23 20:59 ` vb
[not found] ` <mailman.166.1161624291.27805.help-gnu-emacs@gnu.org>
2006-10-23 17:48 ` David Kastrup
2006-10-23 20:03 ` Eli Zaretskii
2006-10-23 18:33 ` Colin S. Miller
2006-10-23 18:58 ` vb
[not found] ` <mailman.169.1161629903.27805.help-gnu-emacs@gnu.org>
2006-10-23 19:46 ` Peter Boettcher
[not found] <mailman.74.1161208352.2130.help-gnu-emacs@gnu.org>
2006-10-20 16:46 ` Sam Peterson
2006-10-19 5:16 help-gnu-emacs
2006-10-20 5:49 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 21:52 help-gnu-emacs
2006-10-18 22:32 ` Peter Dyballa
2006-10-18 23:12 ` vb
2006-10-19 4:25 ` Eli Zaretskii
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=87ac3mu2l0.fsf@hans.local.net \
--to=dieter@duenenhof-wilhelm.de \
--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).