unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: is it possible to «lose» edits when aborting recursive-edits?
Date: Thu, 11 Jan 2024 11:02:58 +0200	[thread overview]
Message-ID: <835y00med9.fsf@gnu.org> (raw)
In-Reply-To: <87bk9sic99.fsf@mat.ucm.es> (message from Uwe Brauer on Thu, 11 Jan 2024 08:02:10 +0100)

> From: Uwe Brauer <oub@mat.ucm.es>
> Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
> Date: Thu, 11 Jan 2024 08:02:10 +0100
> 
> >>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> > What do you mean by "not committed"?
> 
> The did not appear in the commit.
> 
> Here is an example
> 
> Paragraph 1:
> 
> New: blabla
> 
> Paragraph: 2
> 
> New: more blabla blabla
> 
> C-]
> 
> Commit via vc-next-action
> 
> All new parts paragraph 1 are not part of the commit.

Sorry, this is still not detailed enough: how did those "new parts"
appear, and in which buffer?  IOW, what did you do to make these new
parts appear wherever they appeared?

> Possible explanation
> 
> Paragraph 2
> 
> New more blabla 
> 
> Was written on the top-level but Paragraph 1 on some second or higher
> recursive-level and disappeared after having hit C-]

I'm asking for more details about the "was written" part.

It will be the simplest if you describe the commands you invoked
before C-], even if it's just typing some text.  IOW, a complete
recipe of the issue.



  reply	other threads:[~2024-01-11  9:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 20:54 is it possible to «lose» edits when aborting recursive-edits? Uwe Brauer via Emacs development discussions.
2024-01-11  6:42 ` Eli Zaretskii
2024-01-11  7:02   ` Uwe Brauer
2024-01-11  9:02     ` Eli Zaretskii [this message]
2024-01-11 10:01       ` Uwe Brauer
2024-01-11 17:51       ` Uwe Brauer via Emacs development discussions.
2024-01-16  8:20 ` Jean Louis
2024-01-16 14:50   ` [External] : " Drew Adams

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=835y00med9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).