From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: calling desktop-read interactively
Date: Thu, 26 Sep 2019 18:06:52 +0200 [thread overview]
Message-ID: <CAAeL0STpjt5jP_HA9bZE7dCTa+rV7FDffYwtqA-Z__XoLmwGCA@mail.gmail.com> (raw)
In-Reply-To: <jwvtv8z84at.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On Thu, Sep 26, 2019 at 5:32 PM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> but if you
> have different "desktops" for different kinds of sessions (e.g. one for
> email, one for programming, ...) then having to place the desktops in
> different subdirectories feels awkward (especially since there isn't
> necessarily many more files to put in those directories).
My use of desktop.el is very simple, so I've never had that problem. I
don't even use desktop files in project directories, just one in ~/.emacs.d/
But for the sessions case you point out, I would definitely create
subdirectories under ~/.emacs.d/desktop-sessions/ or somesuch. Not
particularly awkward, IMO.
> Being *able* to specify a directory is great. Being limited to that is
odd.
Yes, I agree. It's something to work on, if there's interest.
[-- Attachment #2: Type: text/html, Size: 1086 bytes --]
next prev parent reply other threads:[~2019-09-26 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 2:52 calling desktop-read interactively Juanma Barranquero
2019-09-26 7:30 ` Eli Zaretskii
2019-09-26 12:36 ` Stefan Monnier
2019-09-26 12:53 ` Juanma Barranquero
2019-09-26 15:32 ` Stefan Monnier
2019-09-26 16:06 ` Juanma Barranquero [this message]
2019-09-26 16:31 ` Eli Zaretskii
2019-09-26 16:52 ` Juanma Barranquero
2019-09-26 16:20 ` Drew Adams
2019-09-26 16:28 ` Eli Zaretskii
2019-09-26 19:42 ` Stefan Monnier
2019-09-27 4:59 ` Eli Zaretskii
2019-09-27 12:45 ` Stefan Monnier
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=CAAeL0STpjt5jP_HA9bZE7dCTa+rV7FDffYwtqA-Z__XoLmwGCA@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).