From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Not reloading the desktop; already loaded
Date: Sat, 29 Oct 2022 08:48:26 +0300 [thread overview]
Message-ID: <837d0jji39.fsf@gnu.org> (raw)
In-Reply-To: <5ccf9868-c656-61a7-e5e7-31faba8d4a3a@akwebsoft.com> (message from Tim Johnson on Fri, 28 Oct 2022 11:27:12 -0800)
> Date: Fri, 28 Oct 2022 11:27:12 -0800
> From: Tim Johnson <tim@akwebsoft.com>
>
> > I assume yours is an interactive (i.e., no "--batch") session, so the
> > condition that applies in your case is the one about the "owner" of
> > the desktop file. So the problem is that the desktop file was (of
> > course) written by the same Emacs process as the current one, and you
> > need to work around that. One way is to override the definition of
> > desktop-owner.
> How would I do that? (feel free to point to documentation and I will
> also search
> on your last phrase)
The simplest way is to define your own version of that function that
is similar, but not identical. A less brute-force way is to "advise"
the function; see the node "Advising Functions" in the ELisp manual.
> > Another way is to release the desktop file lock before
> > you load the second one, and then re-lock it afterwards.
> Again: how would I do that?
Look at the functions in desktop.el which do that: desktop-claim-lock
and desktop-release-lock. You can call them from your code.
> > And there
> > are probably others.
> Sure, such as use elisp instead of bash to delete the file lock ...
Deleting the lock is not something I'd recommend. It is there for a
reason.
next prev parent reply other threads:[~2022-10-29 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 22:41 Not reloading the desktop; already loaded Tim Johnson
2022-10-28 0:09 ` Emanuel Berg
2022-10-28 6:03 ` Eli Zaretskii
2022-10-28 19:27 ` Tim Johnson
2022-10-29 5:48 ` Eli Zaretskii [this message]
2022-10-29 15:17 ` Tim Johnson
-- strict thread matches above, loose matches on Subject: below --
2022-10-27 22:24 Tim Johnson
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=837d0jji39.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).