From: GianUberto.Lauri@eng.it (Gian Uberto Lauri)
Cc: help-gnu-emacs@gnu.org, saint@eng.it
Subject: Re: Preserving command history between sessions
Date: Sat, 8 Jan 2005 19:18:09 +0100 [thread overview]
Message-ID: <16864.9185.55734.989680@mail.eng.it> (raw)
In-Reply-To: <B390BAA2-6181-11D9-852B-000D932A32C4@Web.DE>
>>>>> "PD" == Peter Dyballa <Peter_Dyballa@Web.DE> writes:
PD> If you mean buffers and their state, then desktop(.el) is the
PD> answer.
I fear that desktop.el doesn't save M-x history... I bet that's my
fault and I did something stupid preventig desktop.el to do this.
Anyway session.el solves my wife's needs.
Thank you very much everybody!
--
/\ ___
/___/\__|_|\_|__|___Gian Uberto Lauri_____________________
//--\ | | \| | Integralista GNUslamico
\/ e coltivatore diretto di software
prev parent reply other threads:[~2005-01-08 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 6:49 Preserving command history between sessions Gian Uberto Lauri
2005-01-08 10:21 ` Eli Zaretskii
2005-01-08 14:29 ` Peter Dyballa
2005-01-08 18:18 ` Gian Uberto Lauri [this message]
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=16864.9185.55734.989680@mail.eng.it \
--to=gianuberto.lauri@eng.it \
--cc=help-gnu-emacs@gnu.org \
--cc=saint@eng.it \
/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).