From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rainer M Krug <Rainer@krugs.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: org version numbers in file - WAS: Tangling takes long - profiling and calling R
Date: Thu, 18 Jun 2015 10:13:08 +0200 [thread overview]
Message-ID: <87egl977u3.fsf@selenimh.access.network> (raw)
In-Reply-To: <m2616m249u.fsf_-_@krugs.de> (Rainer M. Krug's message of "Wed, 17 Jun 2015 09:16:45 +0200")
Rainer M Krug <Rainer@krugs.de> writes:
> Yes - that's true. But who of the longer org users reads the manual of
> features they use regularly?
Ah well. I turned 3 `mapcar' calls into a single one. It should,
hopefully improve speed in your case (could you confirm it).
Also, I suggest to signal the deprecation in ORG-NEWS (old timers read
it, right?) and remove this part of code during 8.4 development.
WDYT?
> org-lint seems to become the place where these changes can be marked and
> the user be notified - that is really brilliant.
Org Lint is not in master branch, yet.
> I could imagine the following automatic workflow to enable automatic
> linting of org files upon opening when they were saved under an older
> (or unknown) version of org:
>
> 1) a new argument is introduced :
>
> #+FILE_ORG_VERSION: 8.3beta
>
> 2) when opening an org file, this version is checked. The following
> cases are possible:
>
> - parameter not present: assume that file version is older and run org-lint
> - file version older then org version: run org-lint
> - file version identical to org version: just open
> - file version newer: run org-lint
>
> 3) after reviewing the results, org-lint could offer to update the file
> version (#+FILE_ORG_VERSION) to the version of org-mode. This should be, by
> the way, possible to do even when running org-lint manually.
>
> 4) this behavior should be possible to disabled by an additional header
> #+ORG_FILE_VERSION_CHECK: f
> but not via emacs.el as this should be the standard behavior.
The problem is that linting is not exact science. You shouldn't put too
much trust into it.
Also, "version" too broad: despite its name, some syntax changes were
introduced in the middle of "8.3beta".
Therefore, I'm not sure it's worth the hassle.
Regards,
next prev parent reply other threads:[~2015-06-18 8:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 8:39 Tangling takes long - profiling and calling R Rainer M Krug
2015-06-15 8:42 ` Rainer M Krug
2015-06-15 18:52 ` Charles C. Berry
2015-06-16 10:29 ` Rainer M Krug
2015-06-15 19:49 ` Nicolas Goaziou
2015-06-16 10:34 ` Rainer M Krug
2015-06-16 11:46 ` Nicolas Goaziou
2015-06-16 12:45 ` Sebastien Vauban
2015-06-16 13:04 ` Nicolas Goaziou
2015-06-16 14:47 ` Rainer M Krug
2015-07-01 14:03 ` Aaron Ecay
2015-07-02 11:51 ` Nicolas Goaziou
2015-07-02 12:52 ` Rainer M Krug
2015-07-02 16:35 ` Aaron Ecay
2015-07-02 18:21 ` Sebastien Vauban
2015-07-02 18:44 ` Rainer M Krug
2015-07-02 18:43 ` Rainer M Krug
2015-07-02 16:11 ` Aaron Ecay
2015-07-03 13:43 ` Nicolas Goaziou
2015-07-02 18:51 ` Rainer M Krug
2015-06-16 14:42 ` Rainer M Krug
2015-06-16 21:45 ` Nicolas Goaziou
2015-06-17 7:16 ` org version numbers in file - WAS: " Rainer M Krug
2015-06-18 8:13 ` Nicolas Goaziou [this message]
2015-06-18 13:25 ` Rainer M Krug
2015-06-18 13:50 ` Nicolas Goaziou
2015-06-23 9:04 ` Rainer M Krug
2015-06-18 14:23 ` Detlef Steuer
2015-06-23 8:45 ` Rainer M Krug
2015-06-23 9:32 ` Detlef Steuer
2015-06-23 10:57 ` Rainer M Krug
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=87egl977u3.fsf@selenimh.access.network \
--to=mail@nicolasgoaziou.fr \
--cc=Rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@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).