From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: An article about Emacs for TUGboat
Date: Sun, 11 Feb 2018 16:58:02 +0900 [thread overview]
Message-ID: <2A376770-58D9-4864-94AC-9328C3D0F8D0@gmail.com> (raw)
In-Reply-To: <87r2ps3tex.fsf@mbork.pl>
> On Feb 11, 2018, at 15:57, Marcin Borkowski <mbork@mbork.pl> wrote:
>
>
> On 2018-02-11, at 00:27, Jean-Christophe Helary <jean.christophe.helary@gmail.com> wrote:
>
>>> On Feb 11, 2018, at 4:47, Marcin Borkowski <mbork@mbork.pl> wrote:
>>>
>>> My idea is to first explain the
>>> basic concepts of Emacs, and then proceed to AUCTeX and various ways of
>>> customizing Emacs. I would be very glad if some more experienced Emacs
>>> (and TeX) user could read my paper and suggest any enhancements.
>>
>> May I suggest that you put the introduction to Emacs in an annex at the end of the article? Or even, since there are tons of introductions to emacs concepts, why not refer to them instead of writing your own ?
>
> Maybe you misunderstood me.
Very likely :)
> I do not want to put Yet Another Intro to
> Emacs™ there. I just want to explain (on, say, half a page) what Emacs
> is and what are its core ideas, and introduce the language of buffers
> and modes, so that the readers will know what I'm talking about later.
But then, either the user knows what emacs is about and the half page will be redundant, or does not and then the half page won't be enough.
But it really all depends on how you write that so I won't say more, besides that I'd love to help with the proofreading!
Cheers,
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
next prev parent reply other threads:[~2018-02-11 7:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 19:47 An article about Emacs for TUGboat Marcin Borkowski
2018-02-10 19:57 ` Kaushal Modi
2018-02-13 14:15 ` Marcin Borkowski
2018-02-10 23:27 ` Jean-Christophe Helary
2018-02-11 6:57 ` Marcin Borkowski
2018-02-11 7:58 ` Jean-Christophe Helary [this message]
2018-02-12 16:13 ` Sivaram Neelakantan
2018-02-13 14:04 ` Marcin Borkowski
[not found] ` <mailman.8980.1518452060.27995.help-gnu-emacs@gnu.org>
2018-02-12 16:23 ` Emanuel Berg
2018-02-13 14:03 ` Marcin Borkowski
[not found] ` <mailman.9041.1518530621.27995.help-gnu-emacs@gnu.org>
2018-02-13 19:15 ` Emanuel Berg
2018-02-13 14:02 ` Marcin Borkowski
2018-02-12 4:34 ` N. Raghavendra
2018-02-13 14:06 ` Marcin Borkowski
[not found] ` <mailman.8863.1518305243.27995.help-gnu-emacs@gnu.org>
2018-02-12 15:26 ` Emanuel Berg
2018-02-13 14:04 ` Marcin Borkowski
2018-02-13 11:31 ` Eric S Fraga
2018-02-13 19:50 ` Marcin Borkowski
[not found] ` <871shl3zf9.fsf@russet.org.uk>
2018-02-16 12:13 ` Phillip Lord
2018-02-17 4:24 ` Marcin Borkowski
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=2A376770-58D9-4864-94AC-9328C3D0F8D0@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=help-gnu-emacs@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.