From: Richard Kim <emacs18@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] orgguide.texi: Replace spaces with tabs in two menu lines to be consistent with all other menu lines.
Date: Sat, 3 May 2014 11:00:56 -0700 [thread overview]
Message-ID: <qtm1twau3vi.fsf@gmail.com> (raw)
Why this trivial patch? As I make changes to orgguide.texi, I may
invoke texinfo-all-menus-update or texinfo-every-node-update elisp
commands. When I do the spaces are replaced with tabs. I would
rather not have to deal with these changes when I view git diff.
Besides I think using white spaces consistently is a good thing.
I submitted this email following the instruction at
<http://orgmode.org/worg/org-contribute.html>.
Please let me know if I could have done better.
Thanks.
---
doc/orgguide.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/orgguide.texi b/doc/orgguide.texi
index f93b99a..a3470bd 100644
--- a/doc/orgguide.texi
+++ b/doc/orgguide.texi
@@ -211,7 +211,7 @@ Exporting
* ASCII/Latin-1/UTF-8 export:: Exporting to flat files with encoding
* HTML export:: Exporting to HTML
* @LaTeX{} and PDF export:: Exporting to @LaTeX{}, and processing to PDF
-* iCalendar export:: Exporting to iCalendar
+* iCalendar export:: Exporting to iCalendar
Miscellaneous
@@ -2307,7 +2307,7 @@ that planning information can be incorporated into desktop calendars.
* ASCII/Latin-1/UTF-8 export:: Exporting to flat files with encoding
* HTML export:: Exporting to HTML
* @LaTeX{} and PDF export:: Exporting to @LaTeX{}, and processing to PDF
-* iCalendar export:: Exporting to iCalendar
+* iCalendar export:: Exporting to iCalendar
@end menu
@node Export options, The export dispatcher, Exporting, Exporting
--
1.7.9.5
next reply other threads:[~2014-05-03 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 18:00 Richard Kim [this message]
2014-05-06 9:59 ` [PATCH] orgguide.texi: Replace spaces with tabs in two menu lines to be consistent with all other menu lines 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=qtm1twau3vi.fsf@gmail.com \
--to=emacs18@gmail.com \
--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).