emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alex Branham <branham@utexas.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] protocol: allow users to disable warning about old style links
Date: Fri, 16 Jun 2017 16:26:16 +0200	[thread overview]
Message-ID: <87mv98f1pz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878tksb23w.fsf@utexas.edu> (Alex Branham's message of "Fri, 16 Jun 2017 13:31:31 +0200")

Alex Branham <branham@utexas.edu> writes:

> I did report it upstream as a bug. The maintainer is (understandably,
> I think) hesitant to change since 1) old style links continue to be
> supported

But it will break at some point, hence the warning.

> and 2) there’s no way for a browser extension to detect the
> version of org-mode to install. Since new style links aren’t supported
> in older org versions (like what comes shipped with Emacs), that could
> create issues.

True. Note that Org shipped with Emacs is no longer supported.
Hopefully, Emacs 26.1 will ship with a brand new Org mode.

IIUC, one issue is that the developers of the extension wants to support
multiple Org versions. That's fair, but then, they could implement an
option to generate any of the two styles. It would also make the
transition easier when one of them is dropped.

> I changed it to a defvar and modified the warning. That seems simpler to me.
>
> I wasn’t sure if defvars should go into org-compat.el (that file says
> it’s for compatibility issues with older Emacs versions?) or stay
> where it is. I’ve left it where it is for now but I can move it to
> org-compat.el if you want me to.

"org-compat.el" is about compatibility in the broad sense. It should
contain any volatile code, i.e., code that can be removed in a future
major release.

This variable can go in "org-compat".

>>> +(defcustom org-protocol-warn-about-old-links t
>>> +  "If non-nil (the default), issue a warning when org protocol
>>> +receives old style links."

You forgot to update the docstring.

In any case, I think the extension could offer both styles instead of
adding this variable.

Thank you.

Regards,

  reply	other threads:[~2017-06-16 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 12:11 [PATCH] protocol: allow users to disable warning about old style links Alex Branham
2017-06-16  6:13 ` Nicolas Goaziou
2017-06-16 11:31   ` Alex Branham
2017-06-16 14:26     ` Nicolas Goaziou [this message]
2017-06-21 15:27   ` Tyler Smith
2017-06-21 16:01     ` Mario Martelli
2017-06-21 16:24       ` Tyler Smith
2017-06-21 16:34         ` Tyler Smith
2017-06-21 16:51         ` Mario Martelli
2017-06-21 17:09           ` Tyler Smith
2017-06-21 17:17             ` Mario Martelli

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=87mv98f1pz.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=branham@utexas.edu \
    --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).