unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: My humble additions to AUCTeX
Date: Mon, 13 Jan 2014 19:16:50 +0100	[thread overview]
Message-ID: <20140113191650.0fce85c1@aga-netbook> (raw)
In-Reply-To: <87y52j6d3g.fsf@yahoo.fr>

Dnia 2014-01-13, o godz. 17:49:55
Nicolas Richard <theonewiththeevillook@yahoo.fr> napisał(a):

> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> 
> > Hi all,
> >
> > I've recently started putting together some functions to enhance
> > AUCTeX.  Currently, a very limited set is ready (getting info about
> > the "token" (in the TeX sense) at point and movement by tokens)
> 
> Could you state some of the problems you are solving ? ISTR
> token-by-token motion was a problem for me at some point in the past,
> but I think these problems disappeared. I use C-M-f and C-M-b.

Do I guess correctly that you did some (or more) LaTeX typesetting, but
not too much low-level TeX programming, dear Watson? ;)

Imagine this: <!>\these\are\four\tokens, where <!> denotes the point.
Then, C-M-f moves too far; I want to move by one token (i.e. to get
\these<!>\are\four\tokens), not by a whole string of them at the same
level of curly braces.

Also, I want to level up the word commands to token-aware commands.
Imagine this: \these\are\four\tokens<!>.  Now, if you press M-DEL, the
backslash does not get deleted; if I made its syntax "word", pressing
M-DEL would kill *everything* shown here. And I want to be able to kill
just the string "\tokens" with one keystroke.

Notice that, as I hinted at the beginning, strings of consecutive TeX
commands are rather rare in LaTeX documents; but when doing low-level
TeX programming, such situations are *extremely* common, and I'd find
more fine-grained control over movement very useful then.

Last but not least, I aim at commands to work on matching pairs of
\left...\right, \bigl...\bigr etc. delimiters.  Therefore, I want to be
able to walk through the text token by token.  (I did look into
smartparen, and it doesn't seem to be sophisticated enough to do what I
need.)

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University



  reply	other threads:[~2014-01-13 18:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 23:28 My humble additions to AUCTeX Marcin Borkowski
2014-01-13 16:49 ` Nicolas Richard
2014-01-13 18:16   ` Marcin Borkowski [this message]
2014-01-13 20:47     ` Stefan Monnier
2014-01-14  9:57       ` Marcin Borkowski
2014-01-14 10:16         ` Marcin Borkowski
2014-01-15 13:26         ` Stefan Monnier
2015-01-20 15:25       ` Marcin Borkowski
2015-01-20 16:32         ` Artur Malabarba
2015-01-20 16:45           ` Marcin Borkowski
2015-01-20 18:42           ` Stefan Monnier
     [not found]           ` <mailman.18220.1421779378.1147.help-gnu-emacs@gnu.org>
2015-01-21  2:34             ` Rusi
2014-01-14 10:29     ` Nicolas Richard
2014-01-15 17:58       ` Marcin Borkowski
     [not found] <mailman.11758.1389569313.10748.help-gnu-emacs@gnu.org>
2014-01-13 16:35 ` jack-mac
2014-01-13 18:11   ` 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

  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=20140113191650.0fce85c1@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --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.
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).