From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nicolas Richard <youngfrog@members.fsf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Patches on ffap (mainly for latex buffers)
Date: Fri, 07 Aug 2015 11:47:32 -0400 [thread overview]
Message-ID: <jwvzj23p0li.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zj244ooe.fsf@members.fsf.org> (Nicolas Richard's message of "Thu, 06 Aug 2015 13:54:57 +0200")
> * lisp/ffap.el (ffap-string-at-point-mode-alist): Remove useless and
> misleading backslashes from default value.
[...]
> - (file "--:\\\\$\\{\\}+<>@-Z_[:alpha:]~*?" "<@" "@>;.,!:")
> + (file "--:\\\\${}+<>@-Z_[:alpha:]~*?" "<@" "@>;.,!:")
^^
This one as well, AFAIK.
> Subject: [PATCH 3/4] * lisp/ffap.el (ffap-latex-mode): Use kpsewhich if
> available
Looks OK to me.
> + (prefixes '(""
> + "beamertheme"
> + "beamercolortheme"
> + "beamerfonttheme"
> + "beamerinnertheme"
> + "beameroutertheme"))
These prefixes look rather ad-hoc. Do we really need them? Why?
> + ;; is found before point on the current line. It should cover most
^^^
Please put 2 spaces between sentences.
Also some of your lines are more than 80 columns wide. Please try and
avoid that.
> The fourth (and last) patch fixes a problem introduced in commit
> ba6c32b6decaa2a72a3d5f854efd513e8e82c118, where braces were allowed in
> filenames. This is not good for TeX and friends, where braces are
> delimiters, as in \input{foo}.
Looks fine to me, thanks,
Stefan
next prev parent reply other threads:[~2015-08-07 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:54 Patches on ffap (mainly for latex buffers) Nicolas Richard
2015-08-07 15:47 ` Stefan Monnier [this message]
2015-08-07 20:09 ` Nicolas Richard
2015-08-07 21:34 ` Stefan Monnier
2015-08-08 6:48 ` Nicolas Richard
2015-08-09 12:44 ` Nicolas Richard
2015-08-09 16:22 ` Stefan Monnier
2015-08-09 16:46 ` Nicolas Richard
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=jwvzj23p0li.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=youngfrog@members.fsf.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.