From: stardiviner <numbchild@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: Bastien <bzg@gnu.org>,
emacs-orgmode@gnu.org, mail <mail@nicolasgoaziou.fr>
Subject: Re: Document backward-incompatible change in ORG-NEWS? (was: [BUG] Recently master branch commit breaks open file: link)
Date: Tue, 25 Feb 2020 15:02:20 +0800 [thread overview]
Message-ID: <87sgizno8z.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8tGUGBxqUYSxq=_p_f2r1m5SV56Gndj0umAcQNBh_WXMw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Samuel Wales <samologist@gmail.com> writes:
> no opinion on anything but a suggestion.
>
> i really like these little scripts that update your org files so they
> are compatible with new org versions.
>
> perhaps one can give them an argument or something to work on all
> agenda files, or a list of files, or somethign liek that?
Sounds reasonable. Apply function on Org Agenda files will be the most case.
>
> On 2/24/20, Bastien <bzg@gnu.org> wrote:
>> Hi Nicolas,
>>
>> it seems that org-store-link stored links to headlines as
>>
>> [[*TODO headline][headline]]
>>
>> keeping the TODO keyword, if any.
>>
>> This is fixed in master but I won't if we should document this bug
>> fix in ORG-NEWS (or if org-store-link was just momentarily broken.)
>>
>> If org-store-link was storing the todo keyword, perhaps we can add
>> a command similar to this one to help users fix broken links:
>>
>> (defun org-fix-links ()
>> "Fix ill-formatted internal links.
>> E.g. replace [[*TODO Headline][headline]] by [[*Headline][headline]].
>> Go through the buffer and ask for the replacement."
>> (interactive)
>> (visible-mode 1)
>> (save-excursion
>> (goto-char (point-min))
>> (while (re-search-forward org-link-any-re nil t)
>> (let* ((raw (match-string 2))
>> (desc (match-string 3))
>> fix new)
>> (when (and raw desc
>> (string-match-p
>> (concat "^\*" (regexp-opt org-todo-keywords-1)
>> "\\s-+\\(.+\\)$")
>> raw))
>> (setq new (replace-regexp-in-string
>> (concat (regexp-opt org-todo-keywords-1) "\\s-+")
>> "" raw))
>> (set-text-properties 0 (length new) nil new)
>> (setq fix (completing-read "Replace link at point by: "
>> nil nil nil new))
>> (replace-match (format "[[%s][%s]]" fix desc))))))
>> (visible-mode -1))
>>
>> WDYT?
>>
>> --
>> Bastien
>>
>>
- --
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
-----BEGIN PGP SIGNATURE-----
iQFIBAEBCAAyFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAl5UxnwUHG51bWJjaGls
ZEBnbWFpbC5jb20ACgkQG13xyVromsPwpgf/RqdCj+Y5dC+3lRUwPwYsi8crTrYP
tOZdszU/V1mAPaEep8Q2ksJwvYBa/0TaZ7H+3M8rS55Ug9vSzQyZ/vO+MBSQIPu4
GcyWvyl6qxuWsn8YJr/2E5gGrvgCkGXbqf4tW4iSxm5gWT+Ui6wziW+c00++UFR9
40TnIVx5xx/2F3vuJGmXA9cyhm/K1O8rzG/7NUhvxypXZhFrU0Tns1WmeCUWi9/7
DPI+FRIxUBzcUlLhuZq3gHjDoCaIOie69MCFkrDFlHakr8s+rvbzokdff5C0r4vp
DCtdIgEAFUFQvcfD7v4b5+5YiYe6Aq2erX7Jrkhn1Pkguku11xNu17HeFQ==
=QjPn
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2020-02-25 7:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 6:38 [BUG] Recently master branch commit breaks open file: link stardiviner
2020-02-24 8:41 ` Bastien
2020-02-24 12:06 ` stardiviner
2020-02-24 12:15 ` Bastien
2020-02-24 15:09 ` stardiviner
2020-02-24 20:30 ` Bastien
2020-02-24 20:35 ` Document backward-incompatible change in ORG-NEWS? (was: [BUG] Recently master branch commit breaks open file: link) Bastien
2020-02-24 21:31 ` Samuel Wales
2020-02-25 7:02 ` stardiviner [this message]
2020-02-25 9:10 ` Document backward-incompatible change in ORG-NEWS? Nicolas Goaziou
2020-02-25 19:34 ` 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=87sgizno8z.fsf@gmail.com \
--to=numbchild@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=samologist@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).