Re: [O] [PATCH] orgguide.texi: Replace spaces with tabs in two menu lines to be consistent with all other menu lines.

2014-05-06 Thread Bastien
Hi Richard,

Richard Kim emac...@gmail.com writes:

 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.

Thanks for the patch, I applied it on the master branch.

 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.

The page contains instructions on how to add a commit message, those
instructions are useful for documentation too.

See this example commit:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=d3f21067

Thanks!

-- 
 Bastien



[O] [PATCH] orgguide.texi: Replace spaces with tabs in two menu lines to be consistent with all other menu lines.

2014-05-03 Thread Richard Kim
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