emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sergei Nosov <sergei.nosov@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Regression: org-translate-link doesn't work correctly in Org 8.3
Date: Fri, 21 Aug 2015 15:04:40 +0200	[thread overview]
Message-ID: <87bne0okrb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CADi+Rs_nfqS=9mhn_U4OM37HX4s+m6Qy-oN5AzZxwk9yzFEmkw@mail.gmail.com> (Sergei Nosov's message of "Fri, 21 Aug 2015 15:48:10 +0300")

Sergei Nosov <sergei.nosov@gmail.com> writes:

> The jump via C-c C-o didn't work for me. But I figured it out in a
> meanwhile - supposedly, what was previously called "thisfile" link type is
> now called "fuzzy".​ Thanks.

fuzzy are for text search, targets and NAME keywords. I'm not sure what
was the exact definition of "thisfile", since it doesn't appear in the
manual. However, I guess it encompassed custom-id, fuzzy, radio and
coderef link types.

> Sorry, I meant, Org ELPA (http://orgmode.org/elpa/) not MELPA (org is not
> published on MELPA at all). The last published package seem to be
> http://orgmode.org/elpa/org-20150817.tar which doesn't contain the fix. So,
> my question is - when the next package (that contains the fix) will be
> published? Or, alternatively, what's the Org policy for publishing new
> packages to ELPA?

I think Org ELPA's release is updated at least every week.

Regards,

  reply	other threads:[~2015-08-21 13:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  9:58 Regression: org-translate-link doesn't work correctly in Org 8.3 Sergei Nosov
2015-08-19 10:25 ` Bastien
2015-08-19 10:39   ` Nicolas Goaziou
2015-08-19 10:53     ` Sergei Nosov
2015-08-19 10:55     ` Bastien
2015-08-19 13:28       ` Nicolas Goaziou
2015-08-19 13:55         ` Sergei Nosov
2015-08-21 12:11           ` Nicolas Goaziou
2015-08-21 12:48             ` Sergei Nosov
2015-08-21 13:04               ` Nicolas Goaziou [this message]
2015-08-21 18:44                 ` Achim Gratz

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=87bne0okrb.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=sergei.nosov@gmail.com \
    /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).