From: Manuel Uberti via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: larsi@gnus.org, 51260@debbugs.gnu.org
Subject: bug#51260: 29.0.50; smerge-mode: void-variable smerge
Date: Mon, 18 Oct 2021 09:13:40 +0200 [thread overview]
Message-ID: <2fd713fc-45c1-bf5d-f462-f8b562855b73@inventati.org> (raw)
In-Reply-To: <87y26qn6w7.fsf@gnus.org>
On 18/10/21 09:12, Lars Ingebrigtsen wrote:
> Manuel Uberti via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
>> - emacs -Q
>> - M-x toggle-debug-on-error
>> - M-x smerge-mode
>>
>> I now get:
>>
>> Debugger entered--Lisp error: (void-variable smerge)
>> byte-code("\303\10\11\304\305\211\n\205\26\0\3061\24\0\307
>> 0\202\26\0\210\305&\6\207" [smerge smerge-begin-re diff-refine
>> easy-mmode-define-navigation "conflict" nil (error) smerge-refine]
>> 7)
>
> I'm unable to reproduce the problem on the current trunk. Could it be a
> build issue? Does the problem go away if you say "make bootstrap"?
>
No, I actually did build using:
- ./configure --with-harfbuzz --with-native-compilation
- make bootstrap -j16
--
Manuel Uberti
www.manueluberti.eu
next prev parent reply other threads:[~2021-10-18 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 7:08 bug#51260: 29.0.50; smerge-mode: void-variable smerge Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-18 7:12 ` Lars Ingebrigtsen
2021-10-18 7:13 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-10-18 7:14 ` Lars Ingebrigtsen
2021-10-18 7:19 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-18 7:20 ` Lars Ingebrigtsen
2021-10-18 12:27 ` Eli Zaretskii
2021-10-18 12:35 ` Lars Ingebrigtsen
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=2fd713fc-45c1-bf5d-f462-f8b562855b73@inventati.org \
--to=bug-gnu-emacs@gnu.org \
--cc=51260@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=manuel.uberti@inventati.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.