unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53419@debbugs.gnu.org
Subject: bug#53419: 27.1; Occur edit mode should also handle RET properly before the line number
Date: Sat, 22 Jan 2022 16:44:15 +0000	[thread overview]
Message-ID: <p9TBZa_JViDDI8NaED1wMq4QMrQvsfgbaX1XWOL89byltGRCuT83A-g5UA8CAlKcdcDN0B9EwzsICfeipVXgPfluKL471LyX3cWkUgcmudg=@protonmail.com> (raw)
In-Reply-To: <87mtjoj84u.fsf@gnus.org>

> I'm not sure I understand the issue. Could you give a recipe to
> reproduce the problem, starting from "emacs -Q"?

1. start Emacs with -Q, you are in scratch
2. M-x occur  and type the word "file" for the regexp
3. you have one match from the initial scratch message
4. switch to the occur window and press e for edit mode,
   then go to before the line number on the line (2:) and
   press RET
6. RET inserts a newline character which does not make sense
   for occur edit, because the matches are line based

RET should always go the the match location like in non-edit
mode, wherever the cursor is on the matching line, because
adding newlines does not really make sense, not even in edit
mode.






  reply	other threads:[~2022-01-22 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 18:24 bug#53419: 27.1; Occur edit mode should also handle RET properly before the line number ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 11:57 ` Lars Ingebrigtsen
2022-01-22 16:44   ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-23 12:54     ` Lars Ingebrigtsen
2022-01-23 13:05       ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='p9TBZa_JViDDI8NaED1wMq4QMrQvsfgbaX1XWOL89byltGRCuT83A-g5UA8CAlKcdcDN0B9EwzsICfeipVXgPfluKL471LyX3cWkUgcmudg=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53419@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=laszlomail@protonmail.com \
    /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).