From: Martin Steffen <msteffen@ifi.uio.no>
To: Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: unable to kill-emacs due to failure to save buffers (in connection with tramp)
Date: Wed, 17 Aug 2022 04:40:35 +0200 [thread overview]
Message-ID: <8635dvsicc.fsf@login.ifi.uio.no> (raw)
In-Reply-To: <86edxjt11d.fsf@login.ifi.uio.no> (Martin Steffen's message of "Sun, 14 Aug 2022 15:19:58 +0200")
Concerning the problem of being ``stuck'' unable to exit emacs: Indeed,
deleting ~/.cache/org-persist/index (and for good measure additionally
doing (setq org-clock-persist nil)) got me rid of the
problem. Now I can exit emacs in a decent way and especially make use of
emacs-client as editor for commit and log message (being forced to shoot
emacs down for exiting made that impossible, the main-emacs I seldomly
quit....)
Martin
>>>>> "Martin" == Martin Steffen <msteffen@ifi.uio.no> writes:
>>>>> "Stefan" == Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> writes:
>>>
>>> (:variable #29# :persist-file
>>> "d9/6cedfd-05fd-4dc3-8542-ee0bb93ac4b3" :path
>>> "/scp:<login>@192.168.x.x:/var/services/homes/mobileorg/test.org"
>>> :inode 11537641 :hash "672132fcd377562aa49d8dbd0044f1c4")
Stefan> This suggests that the problem is not in Tramp but in
Stefan> `org-persist` (or in your use of it), since it seems to be
Stefan> configured to save the value of some variable (not shown
Stefan> here) into your remote server, and org-persist probably
Stefan> tries to save this variable before exiting Emacs.
Martin> That's a plausible analysis. I was originally pointing
Martin> towards Tramp, as the *Messages* showed things like that
>> Tramp: Sending command ‘exec ssh -l <login> -e none 192.168.x.x’
Martin> i.e., since it's about ``remote'' files, it's tramp that
Martin> tries to do it, but the saving seems, as you said, be
Martin> triggered by ``persist''.
Martin> I will look into that. I was so far not aware that I somehow
Martin> use org-persist (or what its purpose is). I definitely use a
Martin> lot of org-packages, and I don't load or require
Martin> org-persist. The only mentioning of "persist" in my
Martin> org-adaptations is
Martin> (setq org-clock-persist t) (org-clock-persistence-insinuate)
Martin> (though I can't remember why exactly I set that, seems also
Martin> not immediately related to tramp, more about logging).
Martin> Anyway, thanks for directing me to better also look into
Martin> ``persist''.
Martin> Martin
prev parent reply other threads:[~2022-08-17 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 9:19 unable to kill-emacs due to failure to save buffers (in connection with tramp) Martin Steffen
2022-08-14 10:14 ` Michael Albinus
2022-08-14 12:24 ` Martin Steffen
2022-08-14 13:09 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-08-14 13:19 ` Martin Steffen
2022-08-17 2:40 ` Martin Steffen [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=8635dvsicc.fsf@login.ifi.uio.no \
--to=msteffen@ifi.uio.no \
--cc=help-gnu-emacs@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.
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).