From: Okamsn via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Stefan Kangas" <stefan@marxist.se>,
"João Távora" <joaotavora@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: 52342@debbugs.gnu.org
Subject: bug#52342: [PATCH] Add Texinfo support for Flymake
Date: Fri, 10 Dec 2021 01:40:01 +0000 [thread overview]
Message-ID: <2ca03882-cf86-5eef-804f-3cc1f130b71f@protonmail.com> (raw)
In-Reply-To: <CADwFkmkvAe6RUqL5nAHRwRKpZv8rgjjLytoc6o4LRDq9q=qOQA@mail.gmail.com>
On 12/7/21 19:50, Stefan Kangas wrote:
> João Távora <joaotavora@gmail.com> writes:
>
>>> > Don't you dare insert any `require' calls at top level in this file
>>> > --rms.
>>>
>>> which I tried to observe.
>>
>> No comment :-)
>
> That file is really jumping through a lot of hoops to avoid require, for
> some reason. It seems like yet another thing that was probably relevant
> 30 years ago, but not so much today. Personally, I'd just simplify it.
>
Hello,
Would the file `texinfo.el` loading Flymake affect the use of a more
recent version of Flymake installed as a package? I have run into issues
when using Org as a downloaded package, where a library causes the
built-in version to load, which breaks using the newer features.
The file `python.el` doesn't seem to do any loading/declaring of Flymake
features.
Thank you.
next prev parent reply other threads:[~2021-12-10 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 2:48 bug#52342: [PATCH] Add Texinfo support for Flymake Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 14:10 ` Stefan Kangas
2021-12-07 14:23 ` João Távora
2021-12-07 23:39 ` Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 23:43 ` João Távora
2021-12-07 23:46 ` João Távora
2021-12-08 1:00 ` Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-08 1:03 ` Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-19 16:17 ` Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-04 20:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-04 21:00 ` João Távora
2022-04-15 1:12 ` Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-16 21:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 14:25 ` Lars Ingebrigtsen
2021-12-08 0:50 ` Stefan Kangas
2021-12-10 1:40 ` Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-12-10 2:07 ` Stefan Kangas
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=2ca03882-cf86-5eef-804f-3cc1f130b71f@protonmail.com \
--to=bug-gnu-emacs@gnu.org \
--cc=52342@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=okamsn@protonmail.com \
--cc=stefan@marxist.se \
/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).