From: Suhail Singh <suhailsingh247@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72945@debbugs.gnu.org, Suhail Singh <suhailsingh247@gmail.com>
Subject: bug#72945: 29.4; Org: ox-html: attr_html not supported in source code and fixed-width blocks during HTML export
Date: Mon, 02 Sep 2024 08:26:07 -0400 [thread overview]
Message-ID: <871q22jl7k.fsf@gmail.com> (raw)
In-Reply-To: <861q229tsw.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 02 Sep 2024 14:30:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Thanks, but why are you posting this here? ox-html.el is part of Org,
My reasoning was that Org is a part of Emacs, so debbugs would be
appropriate. Or at least, that it would _not be inappropriate_.
Perhaps I was mistaken.
> and I don't see anything in the above discussion that indicates you
> should post these patches to the Emacs bug-tracker. What did I miss?
There was no normative expectation to report these to debbugs, i.e., I
am doing so of my own volition. Reading between the lines of your
response, however, it seems debbugs may not be the right place for it.
If so, apologies for the noise; especially if this was documented
somewhere and I missed it.
My intent was to have a reliable reference that I could either subscribe
to or check semi-regularly, to understand the status of the issue.
Specifically, if/when the issue gets resolved, I'd like to know without
having to monitor all the commits in the Org repository.
I understand that Org uses some custom mailing list software ("Woof!")
to help with tracking issues. However, it's not clear whether that is
exclusively the case (i.e., debbugs is not to be used for Org issues).
On a related note, "Woof!" doesn't list the issue under "Bugs" and I
don't quite understand why:
<https://tracker.orgmode.org/bugs?search=attr_html>.
In any case, thank you for taking the time to look into this.
--
Suhail
next prev parent reply other threads:[~2024-09-02 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 0:55 bug#72945: 29.4; Org: ox-html: attr_html not supported in source code and fixed-width blocks during HTML export Suhail Singh
2024-09-02 1:56 ` bug#72945: [PATCH 1/2] ox-html: Add support for attr_html for source code blocks Suhail Singh
2024-09-02 1:58 ` bug#72945: [PATCH 2/2] ox-html: Add support for attr_html in fixed-width blocks Suhail Singh
2024-09-02 11:30 ` bug#72945: 29.4; Org: ox-html: attr_html not supported in source code and fixed-width blocks during HTML export Eli Zaretskii
2024-09-02 12:26 ` Suhail Singh [this message]
2024-09-02 12:32 ` Eli Zaretskii
2024-09-07 9:26 ` Eli Zaretskii
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=871q22jl7k.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=72945@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 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).