From: Bastien Guerry <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: [Accepted] Re: Bug: UTF-8 characters in #+LINK does not work [7.4]
Date: Mon, 31 Jan 2011 21:36:59 +0100 (CET) [thread overview]
Message-ID: <20110131203659.0EB5187AB@myhost.localdomain> (raw)
In-Reply-To: 87d3nchlkj.fsf@keller.adm.naquadah.org
Patch 568 (http://patchwork.newartisans.com/patch/568/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C87d3nchlkj.fsf%40keller.adm.naquadah.org%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] Re: Bug: UTF-8 characters in #+LINK does not work [7.4]
> Date: Tue, 01 Feb 2011 01:20:28 -0000
> From: Julien Danjou <julien@danjou.info>
> X-Patchwork-Id: 568
> Message-Id: <87d3nchlkj.fsf@keller.adm.naquadah.org>
> To: Matt Lundin <mdl@imapmail.org>
> Cc: Gustav =?utf-8?Q?Wikstr=C3=B6m?= <gustav.erik@gmail.com>,
> emacs-orgmode@gnu.org
>
> On Sat, Jan 29 2011, Matt Lundin wrote:
>
> > The regexp in org-link-expand-abbrev does not allow for accented
> > characters in the link abbreviation. I am not sure whether this is an
> > intended limitation or a bug. :)
>
> I don't see any reason. Patch attached.
>
>
> >From 1ec1e178aaa6a9935819a873ae492be7a2ddb2f6 Mon Sep 17 00:00:00 2001
> From: Julien Danjou <julien@danjou.info>
> Date: Mon, 31 Jan 2011 21:19:07 +0100
> Subject: [PATCH] Allow more char type in link abbrev
>
> * org.el (org-link-expand-abbrev): Allow any type of character
> in link expand.
>
> Signed-off-by: Julien Danjou <julien@danjou.info>
> ---
> lisp/org.el | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lisp/org.el b/lisp/org.el
> index 808c9ed..044d2ac 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -8185,7 +8185,7 @@ call CMD."
>
> (defun org-link-expand-abbrev (link)
> "Apply replacements as defined in `org-link-abbrev-alist."
> - (if (string-match "^\\([a-zA-Z][-_a-zA-Z0-9]*\\)\\(::?\\(.*\\)\\)?$" link)
> + (if (string-match "^\\([^:]*\\)\\(::?\\(.*\\)\\)?$" link)
> (let* ((key (match-string 1 link))
> (as (or (assoc key org-link-abbrev-alist-local)
> (assoc key org-link-abbrev-alist)))
> --
> 1.7.2.3
>
>
prev parent reply other threads:[~2011-01-31 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 8:00 Bug: UTF-8 characters in #+LINK does not work [7.4] Gustav Wikström
2011-01-29 15:04 ` Matt Lundin
2011-01-31 20:20 ` Julien Danjou
2011-01-31 20:36 ` Bastien Guerry [this message]
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=20110131203659.0EB5187AB@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).