From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33476@debbugs.gnu.org
Subject: bug#33476: [PATCH] Fix occur revert with list-matching-lines-jump-to-current-line
Date: Mon, 10 Dec 2018 01:54:14 +0200 [thread overview]
Message-ID: <871s6qmf2x.fsf@mail.linkov.net> (raw)
In-Reply-To: <837egj3zja.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Dec 2018 09:55:05 +0200")
>> I propose to install the patch from OP. This patch avoids the error.
>> It still might behave incorrectly in some cases, but at least it
>> doesn't raise the error.
>
> OK, please push that to emacs-26, and thanks.
Done.
The file admin/notes/repo instructs to use the phrase
"Not to be merged to master" to indicate that it should
not be merged to the master.
But actually `gitmerge-skip-regexp' doesn't match this phrase:
(string-match gitmerge-skip-regexp "; Not to be merged to master")
nil
Should admin/gitmerge.el be fixed to support this phrase
before the next merge to master?
>> >> But still I found a bug in master that can be fixed with another patch.
>> >> The following patch is for Emacs 27:
>> >
>> > What is the bug you found in the master branch?
>>
>> In the master branch when `list-matching-lines-jump-to-current-line'
>> is non-nil, it doesn't show the current line highlighted.
>
> Fine with me.
Done.
next prev parent reply other threads:[~2018-12-09 23:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 21:10 bug#33476: [PATCH] Fix occur revert with list-matching-lines-jump-to-current-line Raimon Grau
2018-11-24 21:54 ` Juri Linkov
2018-11-26 17:54 ` Eli Zaretskii
2018-12-08 9:25 ` Eli Zaretskii
2018-12-08 23:16 ` Juri Linkov
2018-12-09 7:55 ` Eli Zaretskii
2018-12-09 23:54 ` Juri Linkov [this message]
2018-12-10 6:27 ` Eli Zaretskii
2018-12-11 4:40 ` Richard Stallman
2018-12-11 23:07 ` Glenn Morris
2018-12-12 17:07 ` Eli Zaretskii
2018-12-13 0:12 ` Richard Stallman
2018-12-13 8:57 ` Robert Pluim
2018-12-13 21:14 ` Richard Stallman
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=871s6qmf2x.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=33476@debbugs.gnu.org \
--cc=eliz@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.
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.