all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jean Louis <bugs@gnu.support>,
	"60269@debbugs.gnu.org" <60269@debbugs.gnu.org>
Subject: bug#60269: 30.0.50; recursive-edit not completed when buffer killed
Date: Fri, 23 Dec 2022 17:29:48 +0000	[thread overview]
Message-ID: <SJ0PR10MB548840025EEEC11685931B66F3E99@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <868riyoecp.fsf@protected.rcdrun.com>

> I am using many times recursive-edits to edit description, text, values
> in the database. ...
>
> When recursive edit is finished,
> the returning string is recorded in the database as recursive-edit
> remains with the running function waiting for input. Recursive edit
> buffer closes when finished, and that is signal that string is finished
> and shall go into the database.
> 
> If I use ordinary file editing, it is unclear for invoking function when
> is that editing really finished. Or maybe I should add hook and replace
> buffer killing function C-x k with the function to load the saved file
> of the buffer back into the database?
> 
> Any idea is appreciated.

You might want to try library `rec-edit.el':

https://www.emacswiki.org/emacs/RecursiveEdit#rec-edit.el

It can make it more obvious when you're
in a recursive edit, which level, etc.

And you can use the same key, `C-M-c', to
exit a recursive edit and (with `C-u') to
enter one at the top level.

https://www.emacswiki.org/emacs/rec-edit.el

      parent reply	other threads:[~2022-12-23 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  5:53 bug#60269: 30.0.50; recursive-edit not completed when buffer killed Jean Louis
2022-12-23  8:34 ` Eli Zaretskii
2022-12-23  9:04   ` Jean Louis
2022-12-23 17:29 ` Drew Adams [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB548840025EEEC11685931B66F3E99@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=60269@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    /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.