From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: calling desktop-read interactively
Date: Fri, 27 Sep 2019 07:59:11 +0300 [thread overview]
Message-ID: <834l0yl4gw.fsf@gnu.org> (raw)
In-Reply-To: <jwvef027snd.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 26 Sep 2019 15:42:48 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org
> Date: Thu, 26 Sep 2019 15:42:48 -0400
>
> >> if you have different "desktops" for different kinds of sessions
> >> (e.g. one for email, one for programming, ...)
> > Why would you want that, when Emacs has frames, and each frame can be
> > set up for different kinds of jobs?
>
> I always have 2 Emacs sessions running, one for email and one
> for programming. Each session uses many frames. I use separate
> sessions for them because I don't want to have one operation block
> the other (mostly: my email-session being blocked while
> sending/receiving messages).
Starting Emacs from different directories for each session should
satisfy this use case. Although I don't think I understand why the
email session needs a desktop file anyway -- what important
information is saved in that desktop file?
next prev parent reply other threads:[~2019-09-27 4:59 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l0yl4gw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--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 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.