From: Alain.Cochard@unistra.fr
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Alain.Cochard@unistra.fr, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Suspected bug: '#+STARTUP: indent' messes up inlinetasks' tag alignment
Date: Fri, 19 Aug 2022 14:14:58 +0200 [thread overview]
Message-ID: <25343.32450.336604.84364@gargle.gargle.HOWL> (raw)
In-Reply-To: <87tu6g7iul.fsf@localhost>
Ihor Radchenko writes on Sat 13 Aug 2022 14:33:
> Can you try the attached patch?
The problem is solved if I use emacs 28.1 (thanks a lot), but not for
emacs 27.2...
Emacs 27.2 is the native emacs for the Fedora 34 GNU/Linux
distribution I use. I was able to install emacs 28.1 from source, but
I couldn't have my MUA (vm) work properly with it, so it would be
great if you could find a fix valid for emacs 27.2 too!
PS: I have had only a very limited and ancient experience with
patches, so it was not immediate for me to try your patch. While
working on it, I noticed that the section of the manual
* Feedback:: Bug reports, ideas, patches, etc.
does not even contain the word 'patch'. So I was thinking it might be
a good idea to say a few words in that section about what patches are
and how to apply them.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
next prev parent reply other threads:[~2022-08-19 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 12:40 Suspected bug: '#+STARTUP: indent' messes up inlinetasks' tag alignment Alain.Cochard
2022-08-13 6:33 ` Ihor Radchenko
2022-08-19 12:14 ` Alain.Cochard [this message]
2022-08-20 7:20 ` Ihor Radchenko
2022-08-21 15:13 ` Alain.Cochard
2022-08-22 12:08 ` Ihor Radchenko
2022-08-22 15:17 ` applying patches Max Nikulin
2022-08-23 2:43 ` 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=25343.32450.336604.84364@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).