From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: File specific exporting of tags
Date: Tue, 20 Nov 2007 00:23:38 +0000 [thread overview]
Message-ID: <87ejel229h.fsf@bzg.ath.cx> (raw)
In-Reply-To: <4741EDA9.3080601@gmail.com> (Daniel J. Sinder's message of "Mon, 19 Nov 2007 12:10:17 -0800")
"Daniel J. Sinder" <djsinder@gmail.com> writes:
>> Can you try to adapt the relevant text in org.texi (in the distribution
>> of org-mode) and produce a patch. This would certainly help a lot to get
>> your "problem" fixed.
>
> I do appreciate that providing a patch is a better solution than
> providing information leading to the patch.
Both relevant suggestions and patches are useful. Most of the times a
suggestion will be enough, if it is relevant and accurate (as yours was)
Sometimes patches will be okay but, as Carsten told me, Org manual is in
constant move under his fingers, so don't spend too much time on trying
to edit it and send the *perfect patch* :)
> Yes, I'd greatly appreciate help. Some example commands would at
> least make it more likely that producing the patch myself wouldn't
> stagnate due to my perception of the time it would take me to figure
> out how to do it.
Since you're using Emacs, the easiest way to make a patch is this:
- keep the original copy of org.texi somewhere (version A)
- copy it into a working directory (version B)
- edit version B
- in dired, hit `=' on version B
- enter version A at the prompt
- go to the newly opened window containing the diff
- save the diff buffer into something like "org_yourname.texi.patch"
- send it to the list/Carsten
You're done.
HTH,
--
Bastien
next prev parent reply other threads:[~2007-11-20 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 1:38 File specific exporting of tags Daniel J. Sinder
2007-11-19 2:51 ` Bastien
2007-11-19 8:19 ` Egli Christian (KIRO 41)
2007-11-19 20:10 ` Daniel J. Sinder
2007-11-20 0:23 ` Bastien [this message]
2007-11-20 10:31 ` Egli Christian (KIRO 41)
2007-11-20 12:37 ` Bastien
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=87ejel229h.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).