From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to reliably edit a file from within Emacs Lisp and return a string?
Date: Sat, 24 Aug 2019 23:30:01 +0200 [thread overview]
Message-ID: <20190824213001.GC17256@protected.rcdrun.com> (raw)
In-Reply-To: <834l26idy1.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2019-08-24 21:04]:
> > Date: Sat, 24 Aug 2019 20:50:46 +0200
> > From: Jean Louis <bugs@gnu.support>
> > Cc: help-gnu-emacs@gnu.org
> >
> > * Eli Zaretskii <eliz@gnu.org> [2019-08-24 20:26]:
> > > > Date: Sat, 24 Aug 2019 19:37:11 +0200
> > > > From: Jean Louis <bugs@gnu.support>
> > > > Cc: GNU Emacs Help <help-gnu-emacs@gnu.org>
> > > >
> > > > - use simple editing of buffer with kill-buffer-hook, if I can come
> > > > back to initial program execution, as program execution must be wait
> > > > for editing to finish, I do not know how
> > >
> > > A command such as "M-x loop-continue" (possibly bound globally to some
> > > key sequence) should be enough to resolve the "come back to initial
> > > program execution" part.
> >
> > I do not have loop-continue, is it in some package?
>
> That's a command you need to write. It is supposed to go to the next
> field and generate a buffer for the user to edit that field.
I know what you mean. But command that handles next fields is in
the depth 0, I just need to return to senior function, or find
way how to wait on find-file
Jean
next prev parent reply other threads:[~2019-08-24 21:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 21:31 How to reliably edit a file from within Emacs Lisp and return a string? Jean Louis
2019-08-22 22:01 ` Noam Postavsky
2019-08-22 22:46 ` Jean Louis
2019-08-22 23:10 ` Óscar Fuentes
2019-08-22 23:22 ` Noam Postavsky
2019-08-23 1:19 ` Jean Louis
2019-08-23 1:27 ` Noam Postavsky
2019-08-23 7:49 ` Eli Zaretskii
2019-08-23 14:01 ` Jean Louis
2019-08-23 14:14 ` Robert Pluim
2019-08-24 12:20 ` Jean Louis
2019-08-24 12:24 ` Jean Louis
2019-08-23 14:25 ` Eli Zaretskii
2019-08-24 12:19 ` Jean Louis
2019-08-24 12:30 ` Eli Zaretskii
2019-08-24 12:41 ` Jean Louis
2019-08-24 13:17 ` Eli Zaretskii
2019-08-24 14:14 ` Jean Louis
2019-08-24 14:55 ` Jean Louis
2019-08-24 15:10 ` Eli Zaretskii
2019-08-24 15:51 ` Jean Louis
2019-08-24 16:11 ` Eli Zaretskii
2019-08-24 16:44 ` Jean Louis
2019-08-24 16:55 ` Eli Zaretskii
2019-08-24 17:02 ` Eli Zaretskii
2019-08-24 17:17 ` Jean Louis
2019-08-24 17:23 ` Eli Zaretskii
2019-08-24 17:37 ` Jean Louis
2019-08-24 18:25 ` Eli Zaretskii
2019-08-24 18:50 ` Jean Louis
2019-08-24 19:03 ` Eli Zaretskii
2019-08-24 21:30 ` Jean Louis [this message]
2019-08-24 17:15 ` Jean Louis
2019-08-24 17:22 ` Eli Zaretskii
2019-08-24 16:18 ` Yuri Khan
2019-08-24 17:07 ` Jean Louis
2019-08-24 13:08 ` Jean Louis
2019-08-23 21:44 ` Marcin Borkowski
2019-08-24 12:15 ` Jean Louis
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=20190824213001.GC17256@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=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).