emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien Guerry <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: [Accepted] [Orgmode, 1/2] Only match complete words in org-export-add-options-to-plist
Date: Sun, 13 Feb 2011 00:49:00 +0100 (CET)	[thread overview]
Message-ID: <20110212234900.7FCAF8860@myhost.localdomain> (raw)
In-Reply-To: 1c07dac7fa0dd036dec6a1147fde83c5cddf8639.1295529378.git.wence@gmx.li

Patch 551 (http://patchwork.newartisans.com/patch/551/) is now "Accepted".

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3C1c07dac7fa0dd036dec6a1147fde83c5cddf8639.1295529378.git.wence%40gmx.li%3E

Here is the original message containing the patch:

> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [Orgmode,
> 	1/2] Only match complete words in org-export-add-options-to-plist
> Date: Thu, 20 Jan 2011 18:23:22 -0000
> From: Lawrence Mitchell <wence@gmx.li>
> X-Patchwork-Id: 551
> Message-Id: <1c07dac7fa0dd036dec6a1147fde83c5cddf8639.1295529378.git.wence@gmx.li>
> To: emacs-orgmode@gnu.org
> Cc: Lawrence Mitchell <wence@gmx.li>
> 
> * org-exp.el (org-export-add-options-to-plist): Require match to start
> at a word-boundary.
> 
> Previously, if an option was the suffix of another option (such as TeX
> and LaTeX) the setting for the former would propagator to the latter.
> This seems like an unintended consequence of a lax regexp in
> org-export-add-options-to-plist.  This patch allows options to share a
> suffix with another option by requiring that the match against an
> option starts at a word-boundary.
> 
> ---
> lisp/org-exp.el |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/lisp/org-exp.el b/lisp/org-exp.el
> index 9954227..d099c82 100644
> --- a/lisp/org-exp.el
> +++ b/lisp/org-exp.el
> @@ -824,7 +824,7 @@ security risks."
>        (let ((op org-export-plist-vars))
>  	(while (setq o (pop op))
>  	  (if (and (nth 1 o)
> -		   (string-match (concat (regexp-quote (nth 1 o))
> +		   (string-match (concat "\\<" (regexp-quote (nth 1 o))
>  					 ":\\([^ \t\n\r;,.]*\\)")
>  				 options))
>  	      (setq p (plist-put p (car o)
> 

  reply	other threads:[~2011-02-12 23:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 13:23 [PATCH 0/2] References auto-generated labels with \ref in LaTeX export Lawrence Mitchell
2011-01-20 13:23 ` [PATCH 1/2] Only match complete words in org-export-add-options-to-plist Lawrence Mitchell
2011-02-12 23:49   ` Bastien Guerry [this message]
2011-01-20 13:23 ` [PATCH 2/2] Allow option of using bare \ref links in LaTeX export Lawrence Mitchell
2011-02-12 23:46 ` [PATCH 0/2] References auto-generated labels with \ref " Bastien

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110212234900.7FCAF8860@myhost.localdomain \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).