From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to persist registers across sessions?
Date: Thu, 30 Jun 2022 19:01:06 +0300 [thread overview]
Message-ID: <83bkuaf8e5.fsf@gnu.org> (raw)
In-Reply-To: <Yr20S5eO2ISr/OzU@protected.localdomain> (message from Jean Louis on Thu, 30 Jun 2022 17:33:47 +0300)
> Date: Thu, 30 Jun 2022 17:33:47 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: help-gnu-emacs@gnu.org
>
> > Is anything wrong with using desktop-save-mode?
>
> For me that is so little useful. Imagine having 2-3 windows and
> particular flow, but also other 100 buffers. User may wish to save
> that visible window configuration and not all of the buffers
> available inside of Emacs.
Knock yourself out, if you want, but I think you underestimate the
problem before you. E.g., how can you save just the window
configuration without also saving which files were visited by each of
the window, where was the point in each buffer, what were your local
variables and minor modes, perhaps the mark position in each buffer,
maybe the last search string etc.? desktop.el has all of that already
figured out, and gives you useful customization variables to decide
what you'd like to save/restore.
> desktop-save is so much complex in its operation. I do not use it
> for that reason.
I wonder why it matters how complex the software is if it does the
job. Emacs itself is orders of magnitude more complex than
desktop.el, but you still use it to your benefit, as do I and everyone
else on this list.
next prev parent reply other threads:[~2022-06-30 16:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 3:24 How to persist registers across sessions? Pankaj Jangid
2022-06-27 12:01 ` Michael Heerdegen
2022-06-28 18:03 ` Jean Louis
2022-06-29 15:35 ` Visuwesh
2022-06-30 12:50 ` Jean Louis
2022-06-30 13:55 ` Michael Heerdegen
2022-06-30 14:00 ` Eli Zaretskii
2022-06-30 14:23 ` Michael Heerdegen
2022-06-30 15:50 ` Eli Zaretskii
2022-06-30 14:33 ` Jean Louis
2022-06-30 16:01 ` Eli Zaretskii [this message]
2022-06-30 21:55 ` Jean Louis
2022-07-01 6:02 ` Eli Zaretskii
2022-07-01 7:03 ` Jean Louis
2022-07-01 7:19 ` Eli Zaretskii
2022-07-01 12:27 ` Jean Louis
2022-07-02 5:54 ` Eli Zaretskii
2022-07-02 8:46 ` Jean Louis
2022-07-02 9:04 ` Eli Zaretskii
2022-07-02 17:19 ` Jean Louis
2022-07-02 17:40 ` Eli Zaretskii
2022-07-02 18:03 ` Jean Louis
2022-07-02 18:42 ` Eli Zaretskii
2022-07-02 18:52 ` Jean Louis
2022-07-03 5:02 ` Eli Zaretskii
2022-07-01 14:29 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-01 16:07 ` [External] : " Drew Adams
2022-07-02 11:00 ` Pankaj Jangid
2022-07-02 11:48 ` Eli Zaretskii
2022-07-04 3:26 ` Pankaj Jangid
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=83bkuaf8e5.fsf@gnu.org \
--to=eliz@gnu.org \
--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).