emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)]
Date: Wed, 27 Oct 2021 00:11:49 +0700	[thread overview]
Message-ID: <sl9csn$14r$1@ciao.gmane.io> (raw)
In-Reply-To: <87bl3dggbp.fsf@gnu.org>

On 26/10/2021 00:33, Bastien wrote:
> Ihor Radchenko writes:
> 
>> I am thinking to revert the patch and reopen (BTW, how to do it in
>> Woof!?) this bug report for now.
> 
> Sure, please go ahead, thanks.
> 
> PS: I'm not sure how to do this with Woof! but I'm working on the next
> version of Woof! where this will be possible.

Would not it be enough to just add X-Woof-Bug header to the message? 
Maybe even with "(Reopened)" suffix to the title to warn other people 
that it is not a forgotten bug, even if they remember that some patch 
was committed. It is a wild guess, I did not looked into the "Woof!" 
code. I just assume that logic inside is not overcomplicated.




  parent reply	other threads:[~2021-10-26 17:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 11:46 Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)] Dr. Arne Babenhauserheide
2021-10-01  9:56 ` Ihor Radchenko
2021-10-02  4:30   ` Bastien
2021-10-02  4:52     ` Ihor Radchenko
2021-10-02  4:59       ` Bastien
2021-10-02  5:25         ` Ihor Radchenko
2021-10-25 12:57         ` Ihor Radchenko
2021-10-25 17:33           ` Bastien
2021-10-26  6:44             ` Greg Minshall
2021-10-26  6:56               ` Bastien
2021-10-26  7:33                 ` Greg Minshall
2021-10-26 17:11             ` Max Nikulin [this message]
2021-10-27  7:08               ` (Reopened) Bug: font-lock error with - in code-mode Ihor Radchenko
2021-10-27 11:50                 ` Cancel "yes" entry on updates.orgmode.org (was: Re: Bug: font-lock error with - in code-mode) Max Nikulin
2021-10-27 16:51                   ` Max Nikulin
2021-10-02  5:07       ` Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)] Ihor Radchenko
2021-10-28 14:03   ` Bug: font-lock error with - in code-mode (reopened) Max Nikulin
2021-10-28 14:16     ` Ihor Radchenko

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='sl9csn$14r$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).