all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: An article about Emacs for TUGboat
Date: Fri, 16 Feb 2018 12:13:30 +0000	[thread overview]
Message-ID: <WM!3666f33c7b21c6b22cae55266ab11cfdbce1bb4daba0d9575dbe39376d539e2ff55cc22269c010087edb5744b26e9d6b!@mailhub-mx3.ncl.ac.uk> (raw)
In-Reply-To: <87tvuo4oez.fsf@mbork.pl> (Marcin Borkowski's message of "Sat, 10 Feb 2018 20:47:48 +0100")


You might also be interested in adding some more geeky stuff such as the
Rweave support in ESS, polymode or my own lentic which allows advanced
literate programming.

Phil


Marcin Borkowski <mbork@mbork.pl> writes:

> Hi all,
>
> I was asked by one of the editors of TUGboat (the journal of the TeX
> Users' Group) to write an article about using Emacs for TeX.  I am now
> in the process of writing this paper.  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.
>
> For the record, I want to explain Emacs using four main concepts:
>
> 1. Buffers.  Like in Unix "everything is a file", in Emacs "everything
> is a buffer".  What in other editors is implemented using various things
> (dialog windows, text input boxes, non-editable text areas, file
> selection widgets, tree-like outlines etc.) is all buffers in Emacs.
>
> 2. Commands.  Commands are pieces of Lisp which perform various tasks,
> from inserting a character in a buffer to playing tetris.  By writing
> commands, the user can extend Emacs, or in fact build their own editor
> (or other application, like an email client!) on top of it.
>
> 3. Keybindings.  In Emacs, every key can be bound to a command.
>
> 4. Modes.  This is how Emacs knows which key is bound to which command
> in which buffer, thus making the previous three work well together and
> enabling a smooth user experience.
>
> I understand this is an oversimplification - it must be in a 5-10-page
> paper - but I think this more or less catches the spirit of Emacs.  Does
> anyone think I should add (or subtract;-)) something?
>
> Also, are there any volunteers to proofread the first draft of my paper?
> (It should be ready in about a week, and I have to submit it in about
> a month.)
>
> TIA,
>
> --
> Marcin Borkowski



  parent reply	other threads:[~2018-02-16 12:13 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
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 [this message]
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='WM'\!'3666f33c7b21c6b22cae55266ab11cfdbce1bb4daba0d9575dbe39376d539e2ff55cc22269c010087edb5744b26e9d6b'\!'@mailhub-mx3.ncl.ac.uk' \
    --to=phillip.lord@russet.org.uk \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@mbork.pl \
    /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.