From: Ihor Radchenko <yantar92@gmail.com>
To: Alain.Cochard@unistra.fr
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Suspected bug: '#+STARTUP: indent' messes up inlinetasks' tag alignment
Date: Mon, 22 Aug 2022 20:08:35 +0800 [thread overview]
Message-ID: <87wnb0scos.fsf@localhost> (raw)
In-Reply-To: <25346.19351.105465.183755@gargle.gargle.HOWL>
Alain.Cochard@unistra.fr writes:
> > Applying patches is out of scope of the manual.
>
> Fair enough, but in that case shouldn't the word "patches" be removed
> from "Bug reports, ideas, patches, etc."?
The word "patches" refers to sending patches, not applying or testing.
It only makes sense for people who know how to create patches.
In addition, we have https://orgmode.org/worg/org-contribute.html
detailing how to propose patches to Org.
On the other hand, testing the proposed patches is also a kind of
Feedback and can be thought as fitting to the manual section.
> > Next time, you can just ask to provide an alternative way of testing. I
> > can then just upload the patched version to an alternative repository.
>
> Well, I was trying to save you some time so that you can spend it on
> more constructive actions. I succeeded, and learned things in the
> process -- patching (at least basic concepts and actions) is
> relatively simple, so I think it could easily be _within_ the scope of
> the manual.
It might. It is probably even useful. Would you mind writing several
paragraphs for the manual about applying patches?
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-08-22 12:08 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
2022-08-20 7:20 ` Ihor Radchenko
2022-08-21 15:13 ` Alain.Cochard
2022-08-22 12:08 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnb0scos.fsf@localhost \
--to=yantar92@gmail.com \
--cc=Alain.Cochard@unistra.fr \
--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 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.