From: Eli Zaretskii <eliz@gnu.org>
To: Shakthi Kannan <shakthimaan@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Documenting NEWS features for 25.1
Date: Tue, 29 Dec 2015 18:59:29 +0200 [thread overview]
Message-ID: <83h9j1dwcu.fsf@gnu.org> (raw)
In-Reply-To: <CABG-yt11VrFQ1z=mJrGUFiRJAjXtWMSMvUehAL=tV+gr2nP5Dw@mail.gmail.com> (message from Shakthi Kannan on Mon, 28 Dec 2015 22:55:50 +0530)
> Date: Mon, 28 Dec 2015 22:55:50 +0530
> From: Shakthi Kannan <shakthimaan@gmail.com>
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> Attached is a patch for "Document TeX mode custom variable and
> prettify symbols".
Thanks. A few comments below.
> +with the Greek lambda character @samp{λ}. In a TeX buffer, it will
^^ ^^^
Two spaces between sentences, please (we use the US English
conventions).
Also, please use @TeX{} for "TeX", the result looks prettier in the
printed manual and in PDF.
> +replace @samp{\alpha} ... @samp{\omega} and other math macros with
^^^
Please use @dots{} for "...", the result looks prettier in print.
> +their unicode characters. You may wish to use this in non-programming
^^^^^^^ ^^
"Unicode", capitalized. And 2 spaces after the sentence again.
> @@ -1725,7 +1726,12 @@ TeX Print
> to view the @file{.dvi} output is determined by the variable
> @code{tex-dvi-view-command}, regardless of the @TeX{} variant. The
> shell command that @kbd{C-c C-p} runs to print the output is
> -determined by the variable @code{tex-dvi-print-command}.
> +determined by the variable @code{tex-dvi-print-command}. The variable
^^
Two spaces.
> +@code{tex-print-file-extension} can be set to the required file
> +extension for viewing and printing Tex-compiled files. For example,
^^^ ^^
@TeX{} and 2 spaces.
> +you can set it to @code{".pdf"}, and update
The correct markup for file names and their parts is @file{.pdf} (no
quotes are necessary, as @file will supply them).
Thanks again for working on this.
next prev parent reply other threads:[~2015-12-29 16:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151212115202.16784.72345@vcs.savannah.gnu.org>
[not found] ` <E1a7iiY-0004NK-Ky@vcs.savannah.gnu.org>
2015-12-15 1:36 ` [Emacs-diffs] emacs-25 3e14bad: Document new features of Prettify Mode John Wiegley
2015-12-15 3:39 ` Eli Zaretskii
2015-12-15 6:10 ` John Wiegley
2015-12-15 17:51 ` Shakthi Kannan
2015-12-15 17:58 ` Documenting NEWS features for 25.1 (was: [Emacs-diffs] emacs-25 3e14bad: Document new features of Prettify Mode) John Wiegley
2015-12-15 18:34 ` Eli Zaretskii
2015-12-16 6:09 ` Shakthi Kannan
2015-12-16 6:44 ` Documenting NEWS features for 25.1 John Wiegley
2015-12-16 7:59 ` Shakthi Kannan
2015-12-16 10:20 ` Eli Zaretskii
2015-12-16 10:36 ` Shakthi Kannan
2015-12-16 11:11 ` Eli Zaretskii
2015-12-16 12:29 ` Shakthi Kannan
2015-12-21 17:09 ` Shakthi Kannan
2015-12-21 17:28 ` Eli Zaretskii
2015-12-24 16:49 ` Shakthi Kannan
2015-12-25 14:24 ` Eli Zaretskii
2015-12-28 17:25 ` Shakthi Kannan
2015-12-29 16:59 ` Eli Zaretskii [this message]
2015-12-29 17:05 ` Spaces after periods (was: Documenting NEWS features for 25.1) John Wiegley
2015-12-29 17:30 ` Spaces after periods David Kastrup
2015-12-29 17:32 ` Spaces after periods (was: Documenting NEWS features for 25.1) Nikolai Weibull
2015-12-29 17:58 ` Ingo Lohmar
2015-12-29 19:05 ` Marcin Borkowski
2015-12-29 21:05 ` Nikolai Weibull
2015-12-30 7:46 ` Spaces after periods Random832
2015-12-30 7:59 ` Nikolai Weibull
2015-12-29 18:15 ` Spaces after periods (was: Documenting NEWS features for 25.1) Eli Zaretskii
2015-12-29 19:56 ` Spaces after periods John Wiegley
2015-12-30 5:40 ` Documenting NEWS features for 25.1 Shakthi Kannan
2015-12-30 17:49 ` Eli Zaretskii
2015-12-31 5:33 ` Shakthi Kannan
2016-01-11 12:02 Shakthi Kannan
2016-01-11 18:20 ` Eli Zaretskii
2016-01-12 4:28 ` Shakthi Kannan
2016-01-12 15:45 ` Eli Zaretskii
2016-01-12 15:55 ` Shakthi Kannan
2016-01-12 16:08 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2016-01-19 16:49 Shakthi Kannan
2016-01-19 18:39 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h9j1dwcu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=shakthimaan@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.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).