Re: [O] Separate Org file from Subtree

[Bastien Guerry]

Hi Simon,

with a recent Org (8.0) :

- load ox-org.el (require 'ox-org)
- go to your heading
- trigger the export menu with C-c C-e
- restrict to the subtree with C-s
- export as an Org file with O o

HTH,

-- 
 Bastien

Re: [O] #+TOC: figures in ox-html?

[Bastien Guerry]

Hi Melanie,

Melanie Bacou m...@mbacou.com writes:

 The `#+TOC: tables` construct does export nicely to HTML. Just
 wondering if `#+TOC: figures` and maybe `#+TOC: equations` is on the
 roadmap, or could anyone provide a hook to make this work in the
 meantime?

It would be useful to have, yes, I noted this down.

Thanks,

-- 
 Bastien

Re: [O] Publishing orgmode files

[Bastien Guerry]

Hi Xavier,

Xavier Maillard xav...@maillard.im writes:

 I am trying to publish my org project but I am lost in the way I can
 tweak my projects.

 Is there some good tutorial I can follow step by step in order to
 publish several files at once ?

Did you end up with good guidelines?  Either from someone else or from
your own experience?

Thanks in advance for sharing!

-- 
 Bastien

Re: [O] fontenc makes pdf non-searchable

[Bastien Guerry]

Hi Martin,

Martin Leduc mart...@hotmail.com writes:

 However, when opening the experted pdf (with evince or okular) and
 searching for a word, the output from the search function is a list
 of words with apparently incorrect character encoding.

 I get the same result when compiling directly the exported tex file.
 However, if I remove the line:

 \usepackage[T1]{fontenc}

 the compiled pdf becomes correctly interpreted by the search
 function. According to the documentation of the org-article latex
 class, There is no facility to disable loading fontenc.

 What should I do to make the pdf searchable with the org exporter ?

I would try to remove the relevant entry from
`org-latex-default-packages-alist'.  Did you try this?

-- 
 Bastien

Re: [O] [BUG] org-collector.el broken by 8.3 beta

[Bastien Guerry]

Hi Charles,

Charles Millar mill...@verizon.net writes:

 org-collector works as expected using

 GNU Emacs 24.4.1 (i586-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2015-03-07 on binet, modified by Debian
 Org: 8.2.10 release_8.2.10

 but fails if

 GNU Emacs 24.4.1 (i586-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2015-03-07 on binet, modified by Debian
 Org: 8.3beta release_8.3beta-1030-g65bbb1

Can you be more specific on the kind of failure do you have?

-- 
 Bastien

Re: [O] radio targets, a bug?

[Bastien Guerry]

Hi Thomas,

thomas kalbe thomas.ka...@googlemail.com writes:

 (after that comes a number of weird symbols that I cannot even copy
 into the email...)

What version of Org are you using?

M-x org-version RET

Thanks,

-- 
 Bastien

Re: [O] library-of-babel location

[Bastien Guerry]

Hi Charles,

Charles Millar mill...@verizon.net writes:

 From the org manual

 14.6 Library of Babel
 * * * *
 The central repository of code blocks in the “Library of Babel” is
 housed in an Org mode
 file located in the ‘contrib’ directory of Org mode.

 However (at least in my case, Org-mode version 8.2.10 and also
 Org-mode version 8.3beta (release_8.3beta-1316-ga70604)

 the lob is located in the 'doc' directory

 /path/to/org-mode/doc/library-of-babel.org

 So should the does the manual need updating or correction?

Done, thanks.

-- 
 Bastien

Re: [O] [ANN] Table optimizations

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 I committed some changes to org-table.el in order to make them slightly
 more responsive in large buffers. I also refreshed some old code so as
 to prepare for lexical binding switching.

Great, thanks!

-- 
 Bastien

Re: [O] Offline until July, 18

[Bastien Guerry]

Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 I'll be offline for an extended week. Let it not prevent anyone from
 releasing Org 8.3 meanwhile...

I'm late but done!  :)

-- 
 Bastien

Re: [O] Can org-info.js fold top level only?

[Bastien Guerry]

Hi Tom,

Tom adatgyu...@gmail.com writes:

 I tried javscript folding of exported web pages following
 the instructions here:

 http://orgmode.org/manual/JavaScript-support.html

 It works nicely, the top level headlines are initially collapsed and 
 they can be opened with a click, however a click exposes all
 the lower level headlines under the top level headline and ther contents
 recursively.

 Can org-info.js open only one level of headlines (the ones immediately
 under the header clicked) without opening all the headlines and contens
 under them?

AFAIK, we don't have a maintainer for org-info.js -- which is a pity,
given how useful it is.

Anyone with some good HTML/JS knowledge?

Or are we all affected by the javascript frameworks fatigue syndrome?
http://www.allenpike.com/2015/javascript-framework-fatigue/

Thanks in advance for those who want to put some magic on Org through
a web browser.

-- 
 Bastien

Re: [O] Org open link in new window

[Bastien Guerry]

Hi Tory,

torys.ander...@gmail.com (Tory S. Anderson) writes:

 Navigating through the labyrinth of org commands and wrappers, I've
 not been able to find out if there's already a way to open a link
 (particularly a footnote link) in a new window, so that I could retain
 my in-line location and context while reading the linked/footnoted
 text. I realize this functionality is probably out there, but I'm not
 seeing it in the manual section on links. How can I open links in new
 window (splitting my screen)?

Did you find `org-link-frame-setup'?

HTH,

-- 
 Bastien

Re: [O] org-20150629 fails to install if gpg is not present (emacs 24.5.1)

[Bastien Guerry]

Hi Vitaly,

Vitaly Lugovskiy vslugov...@gmail.com writes:

 E.g., if installing on cygwin.

What error does the installation process raise?

How did you find out?

Is installing gpg enough?

-- 
 Bastien

Re: [O] [bug] ox-md and ox-man use same shortcut

[Bastien Guerry]

Hi Brice,

Brice Waegenire brice@gmail.com writes:

 Both ox-man and ox-md use m as their menu-entry shortcut. Witch make
 them merge as one in the org-export-dispatch if they are both loaded
 at the same time.
 Maybe ox-man should use M instead of m.

This is now the case (confirming now as I don't see any confirmation
on the list).

Thanks,

-- 
 Bastien

Re: [O] org-tag-alist - more tags in one keystroke

[Bastien Guerry]

Hi David,

David Belohrad da...@belohrad.ch writes:

 ^^^ the above does not work. Is there any way how to make it
 working?

This can't be done the way you tried, but I'd use registers for this:

(set-register ?a :adam:alice:joe:bill)

Then call C-x r i a to insert it.

Or maybe some other mechanism.

HTH,

-- 
 Bastien

Re: [O] Testers / Feedback wanted: Gantt charts via org-gantt.el

[Bastien Guerry]

Hi Bernhard,

this is really nice!  Would you like to have this library
added to the contrib/ directory of org-mode?

Thanks for your work on this,

-- 
 Bastien

Re: [O] Is it possible to remove org-completing-read and org-completing-read-no-i?

[Bastien Guerry]

Hi,

Rasmus ras...@gmx.us writes:

 I think we had a discussion following another thread on this topic
 (probably a thread you started), and I believe switching to
 `completing-read' is on the table after 8.3 has been released...

Yes.  Can someone take this?

-- 
 Bastien

Re: [O] [PATCH] contrib: rip out org-jira

[Bastien Guerry]

Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Could you provide patch with a proper commit message, using
 format-patch?

I pushed this patch.  Mitchel, thanks for adding a changelog
for your next patch.

-- 
 Bastien

Re: [O] Backports from Emacs repo

[Bastien Guerry]

Hi Kyle,

Kyle Meyer k...@kyleam.com writes:

 I've backported changes touching Org files in the main Emacs repo
 (lisp/org/*.el, doc/misc/org.texi, and etc/refcards/orgcard.tex) since
 the last Org mode sync with Emacs.  These changes are in the temporary
 branch 'backport-master'.  I'll wait to perform the actual merge to
 master until after Nicolas returns.  In the meantime, feel free to let
 me know if you have any comments or issues with the backports or with
 how the conflicts are resolved.

I just merged the branch.  I ran the tests with no problem on your
branch and on the merged master.

Thanks *a lot* for maintaining this branch!

-- 
 Bastien

Re: [O] [ANN] org-dial

[Bastien Guerry]

Hi Michael,

Michael Strey mst...@strey.biz writes:

 ~org-dial~ --- softphone support for Emacs Org mode

 is published on Github now.

 https://github.com/mistrey/org-dial

Oh, nice, thanks.

Now we should consider opening a hotline for Org users.

:)

-- 
 Bastien

Re: [O] latest org from Elpa error: Invalid function: org-babel-header-args-safe-fn

[Bastien Guerry]

Xebar Saram zelt...@gmail.com writes:

 just updated org today and now i get this error on startup:

 Invalid function: org-babel-header-args-safe-fn

 is this related to the new release?

Can you reproduce the problem with a minimal configuration and share
this minimal configuration?

-- 
 Bastien

Re: [O] [DEV] Bump Emacs requirement to 24.4?

[Bastien Guerry]

Hi,

There is no rush for this change.

I will ask on the emacs-devel mailing list for advice on what seems
best to support.

Rasmus, can you revert the 24.3 requirement on org.el for now ?

Let's not make changes in the master branch that push the decision
when it is not taken yet.

Thanks,

-- 
 Bastien

Re: [O] [OFF TOPIC] almost giving up on emacs email..looking for advice?

[Bastien Guerry]

Hi Matt,

Matt Lundin m...@imapmail.org writes:

 I've configured gnus to sort subscribed groups
 automatically by the number of times accessed, with the least read
 groups falling to the bottom.

This is interesting: could you share this bit of configuration?

Thanks!

-- 
 Bastien

Re: [O] [DEV] Bump Emacs requirement to 24.4?

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Master branch is already 24.3+ (with compilation warnings, 24.4+ without
 them): I committed org-lint.el, moved some libraries to lexical
 binding, etc.

Yes, we should have waited for the decision to be taken for this.

 Is there any reason to avoid requiring at least Emacs 24.3 in
 development branch?

I don't know, but we have only little information on what impact such
a change will have.  Our best move for now is to ask on mailing lists,
collect information, then decide.

Also such a change needs to be advertized correctly, I'd rather have
it for Org 9.0 -- same for dropping XEmacs compatibility.

We don't need to complete the whole 8.x series and may jump to 9.0
soonish, but for the time being, I suggest you create a 9.0 branch
with the 24.3 requirement and changes that cannot go without it.

WDYT?

-- 
 Bastien

Re: [O] [DEV] Bump Emacs requirement to 24.4?

[Bastien Guerry]

Rasmus ras...@gmx.us writes:

 But then what will master hold and what would be the point of it?  It
 sounds like a way to rename master to branch9.0...

The point is to allow committing changes that depend on this
requirement without forcing the requirement on master.

We can also simply revert those change and wait for the decision
to be taken.  This is a matter of waiting ~10 days I'd say.

 Also, Emacs 24.3 was released in March, 2013.  By the time the next Org is
 released, it will be more than 3 years old.

Com'on :)

I'm back for good and don't plan to wait years between releases.
I wish we can release 8.4 at the end of August and 9.0 in October.

My simple point is: let's get more information and let's take a
proper decision.  Let's not force the change.

-- 
 Bastien

Re: [O] [DEV] Bump Emacs requirement to 24.4?

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 AFAIU, the decision was between 24.3 and 24.4.

No.  You asked weather it was fine to require Emacs 24.4 in your
original message, then people pointed out that Emacs 24.3 was still
widely used, then you said it was fine to require Emacs 24.3, just
Emacs 24.4 was icing on the cake.

So the questions are just :

- can we drop XEmacs support?  There seem to be a consensus about
  this (see Achim's message)

- what is the oldest version of Emacs that we should require for
  Org 8.3.1 ?  You proposed 24.4 or 24.3 and I want to check for
  possibly older versions.

FWIW, I'm all for Emacs 24.3, I just need time to think about it
and more information, such as what Robert just sent.

This is not a light decision, as we cannot move back, and I don't
see the need for rushing here.

-- 
 Bastien

Re: [O] sudo uninstall org? Can it be done?

[Bastien Guerry]

Sharon Kimble boudic...@skimble.plus.com writes:

 ╭
 │org-babel-safe-header-args , and I think it said something about the
 | function being void. |
 ╰

A similar error is also reported here:
https://www.reddit.com/r/emacs/comments/3fuq11/org_83_released/

Anyone knows how to reproduce and fix this?

-- 
 Bastien

Re: [O] Why not push?

[Bastien Guerry]

Hi Marcin,

Marcin Borkowski mb...@wmi.amu.edu.pl writes:

 I don't want to be nitpicking, but I'm just curious.  I'm looking at the
 function `org-split-string'.  It uses (two times) the following
 construction:

 (setq list (cons (something) list))

 Is there any particular reason for not using `push' there?

I pushed a tiny clean up here.  Next question is: why not using

(split-string STRING SEPARATORS t)

?

-- 
 Bastien

Re: [O] Emacs-Orgmode Archive search fails

[Bastien Guerry]

Hi Charles,

Charles Millar mill...@verizon.net writes:

 It has been a while since I searched the mailing list archives. Did I
 miss an announcement or is the search engine broken?

Did you get any answer by Lars on this?

Thanks,

-- 
 Bastien

Re: [O] Bug: org-clock-sum filter infinite loop [8.2.10 (8.2.10-34-gc41bbc-elpa @ /home/me/.emacs.d/elpa/org-20150223/)]

[Bastien Guerry]

Hi Stephen y...@groks.org writes:

 I want to sum clock times for items which are in state TODO in the
 agenda.

Does this still happen?  Did you find the roots of the problem?

Thanks,

-- 
 Bastien

Re: [O] Bleeding edge in elpa

[Bastien Guerry]

I believe GNU ELPA should contain the stable release.

Of course, this means we need to have a stable release cycle,
and we should put efforts into that, obviously.

-- 
 Bastien

Re: [O] [PATCH] org-timer.el: Use hh:mm:ss format instead of minutes

[Bastien Guerry]

Hi Brice,

Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Brice Waegenire brice@gmail.com writes:

 Following is ORG-NEWS entry:

 * Incompatible changes
 ** org-timer-default-timer type changed from number to string
 If you have, in your configuration, something like =(setq
 org-timer-default-timer 10)= replace it with =(setq
 org-timer-default-timer 10)=.
 * New features
 ** Countdown timer support hh:mm:ss format
 In addition to setting countdown timers in minutes, they can also be
 set using the hh:mm:ss format.

 Added. Thank you.

Thanks for this feature.

FWIW, I added a ad hoc mechanism to tolerate numbers as the value of
`org-timer-default-timer'.

-- 
 Bastien

Re: [O] Bug: Typo in manual [8.2.10 (release_8.2.10 @ /usr/share/emacs/24.4/lisp/org/)]

[Bastien Guerry]

Hi Reuben,

Reuben Thomas r...@sc3d.org writes:

 The
 default @LaTeX{} output is designed for processing with @code{pdftex} or
 @LaTeX{}

 The last “@LaTeX{}” should presumably be “@code{latex}”.

Yes, this has been fixed, thanks,

-- 
 Bastien

Re: [O] bug in org-habits

[Bastien Guerry]

Hi John and Achim,

John Wiegley  writes:

>> Achim Gratz  writes:
>
>> I don't think so. Search for end of entry can be complex in itself and you
>> would never know if the properties you find by looking back aren't belonging
>> to an entry one level down unless you scanned the whole span again. Also,
>> properties can be any size and you have to search for the beginning of the
>> drawer.
>
> Good point.  Still, the option I'd still choose would be:
>
> org-allow-floating-properties
>
>   If set to `non-nil', the :PROPERTIES: drawer may begin anywhere within
>   an entry. Note that this will slow down many operations due to the
>   additional scan needed, and may lead to incorrect result if similar text
>   is found elsewhere within an entry, which is the recommended and default
>   value for this variable is nil.

I think Achim's points above are very valid, and the flexibility
offered by the option above should be very carefully examined.

I'm trying hard to put aside one day or two for org-mode next week,
I'll come back on this issue then.

Thanks,

-- 
 Bastien

Re: [O] Release 8.3.3

[Bastien Guerry]

Hi Kyle,

Kyle Meyer  writes:

> The only commits missing on our end are two related to bumping the
> copyright years in all files.  Are you OK with me bumping all the
> copyright years in the Org repo today?  contrib too?

Sure, thanks in advance.

Re: [O] [PATCH] Fix property name completion

[Bastien Guerry]

Hi Alexey,

Alexey Lebedeff  writes:

> I've signed FSF papers, and looks like this issue is not fixed yet.
> So here is this patch again.

I confirm your papers are signed since Dec. 14th.  Someone more
knowledgeable about this issue can proceed and commit it if needed.

Thanks,

-- 
 Bastien

Re: [O] How to contribute?

[Bastien Guerry]

Hi Xi Shen,

> I would like to make some code change to org-mode. I followed the
> instruction on http://orgmode.org/worg/org-contribute.html#patches,
> but I got stuck at the first step.

Thanks in advance for your contributions and welcome!

> I send my RSA public key, to the system, but I never got a response.

The system is a human being (me).  :)

I suggest you submit a few patches on the mailing list first,
then Nicolas or other core committers can review and apply them.

When everyone is confident about giving you direct write access,
I add your key.

In the meantime I gave you access to worg, which you can now clone
like this:

~$ git clone orgm...@orgmode.org:org-mode.git

... then commit, and push.

Thanks!

-- 
 Bastien

Re: [O] How to contribute?

[Bastien Guerry]

Hi Alex,

aermo...@mirantis.com writes:

> I'm also thinking of contributing to orgmode, so my question is - is
> there any publicly available contributing guide, being SPOT for
> newcomers?

We have this page: http://orgmode.org/worg/org-contribute.html

In general, clone the org-mode repository like this:
~$ git clone git://orgmode.org/org-mode.git

edit, commit on your branch, create patches with format-patch,
then share patches with the list.

When comfortable enough with contributing regularily, send over
your public key and I'll give you write access to the repository.

Thanks!

-- 
 Bastien

[O] Release 8.3.3

[Bastien Guerry]

Hi all,

I've released Org 8.3.3.

Thanks to everyone for their contributions, and to Nicolas
for being the de facto maintainer.

Kyle, can you check that the soon-to-be-release Emacs branch
does not contain changes that we need to backport into Org?

Rasmus, can you check with John Wiegley on how to merge this
release into Emacs?

Thanks!

-- 
 Bastien

[O] bug#22399: org-mode fontification

[Bastien Guerry]

Kyle Meyer  writes:

>> Thanks for installing this -- Kyle, do you confirm you installed the
>> change in Org's git repo?
>
> Yes, in a4edee4.

Thanks!

-- 
 Bastien

[O] bug#22399: org-mode fontification

[Bastien Guerry]

Hi Stefan and Kyle,

Stefan Monnier  writes:

>> No, I don't have commit rights.  I'll update the Org side, but, for
>> issues that were introduced in the Emacs tree post 24.5, I don't know if
>> it's preferable to also update Emacs instead of waiting for the changes
>> to come over with a full sync.
>
> Looks like there's no Org people following this, so I installed it into
> emacs-25 (IOW it should be fixed in the next (25.0.91) pretest).

Thanks for installing this -- Kyle, do you confirm you installed the
change in Org's git repo?

[O] bug#22472: 25.0.50; org-mode: latex fragments can't be un-rendered after a revert

[Bastien Guerry]

Hi Dima,

Dima Kogan  writes:

> 3. C-c C-x C-l
>
>This renders the latex fragment to show the equation graphically. It
>also tells the user (in the mini-buffer) that C-c C-c will remove the
>rendering, and go back to text

Latest stable version from Org does not use C-c C-c to remove the
rendering.

> 4. M-x revert-buffer
>
>At this point I would expect the render to revert to text, but it
>doesn't. This isn't necessarily a bug. However...

(Why would reverting the buffer unrender the LaTeX fragment if the
text file hasn't change?)

> 5. C-c C-c
>
>Here I ask emacs to un-render the fragment, but it does nothing. If
>#4 isn't a bug, then this is definitely a bug.

AFAIK C-c C-c is not used to remove the rendering anymore.

Any chance you can test with the stable Org from GNU ELPA?

Thanks,

-- 
 Bastien

Re: [O] orgmode display in grep buffers

[Bastien Guerry]

Hi Christian,

Christian Wittern  writes:

> I frequently grep in org-mode files.  Sometimes, especially when the hit is
> on a line with links, the display is long and ugly.  Would it be possible to
> tell grep to display the lines using orgmode syntax? Switching the grep
> buffers to orgmode does not work, the connection to the hit gets
> lost.

An indirect solution, but https://github.com/pinard/org-grep might do
the job for you.

-- 
 Bastien

[O] Release Org 8.3.4

[Bastien Guerry]

Hi all,

Org 8.3.4 is out, a bugfix release.

Enjoy!

-- 
 Bastien

Re: [O] Will there be an updated Org Mode in Emacs 25?

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

>> I would suggest that you push the latest maint branch org version to the
>> master branch of emacs now, so that it would be fairly tested by the time
>> the next to next emacs release happens (25.2?).
>
> My secret plan is to have Org 9.0 merged in Emacs master branch just
> after Emacs 25.1 is released.

It sounds like a good plan to me, and you know better now.

> Meanwhile, I think we can release Org 8.3.5 which, hopefully will be the
> last stable release in the 8.3.X series.

I agree.  Let me know if there is anything special to check before
releasing 8.3.5.  If not, I will release it this afternoon.

Thanks,

-- 
 Bastien

Re: [O] Will there be an updated Org Mode in Emacs 25?

[Bastien Guerry]

Kyle Meyer  writes:

>> I agree.  Let me know if there is anything special to check before
>> releasing 8.3.5.  If not, I will release it this afternoon.
>
> The backports from the main Emacs repo are up-to-date.

Thanks Kyle!

I may still have some time to make the release tonight, waiting for
Nicolas "go".

-- 
 Bastien

Re: [O] Will there be an updated Org Mode in Emacs 25?

[Bastien Guerry]

Nicolas Goaziou  writes:

> Here it is: Go!

Done, thanks!

-- 
 Bastien

[O] Release 8.3.5

[Bastien Guerry]

Hi all,

Org 8.3.5, a minor release, is out.

Thanks again to Nicolas and all the contributors!

Enjoy,

-- 
 Bastien

Re: [O] Why no secure code retrieval

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

> GPG signing tags is OK, but I wouldn't like to request every commit to
> be signed.

Agreed.

>>> I know that https can be a bit tedious to setup so I am not asking for it
>>> (though I do think it would be great if it was enabled on the site in some
>>> fashion).
>>
>> HTTPS is not so tedious these days with Let's Encrypt.
>>
>> https://letsencrypt.org/
>>
>> We should set up HTTPS as well.
>
> It would be nice, indeed. I'm Cc'ing Bastien for his opinion on the
> matter, and a possible step forward.

I discussed possible server enhancements with Robert Klein a few
months ago.

I'm considering paying for a digitalocean instance, with https via
letsencrypt for both the website and git.

I'm also considering switching from our current git setup to using
Gogs (https://gogs.io): this would ease the process of adding new
contributors, welcoming more org repositories, etc.

The other solution would simply to use https://savannah.gnu.org.

One remaining problem for both gogs and savannah is to ensure web
references to commits are correctly redirected, which I think is
one line of nginx configuration.

I'm curious to know what people think about the switch to something
like gogs*.

Thanks,

* gitlab seems too heavy, and I'm more experienced in maintaining
  gogs instances than gitlab instances.

-- 
 Bastien

Re: [O] Why no secure code retrieval

[Bastien Guerry]

Hi Ian,

Ian Barton  writes:

> Not heard of Gogs before, although it looks nice. Another possiblity
> would be gitolite with cgit. Gitolite is very flexible and as a
> consequence can be hard to set up initially. The documentation is very
> comprehensive. It supports mirroring of repos.

I have no experience with gitolite.

I encourage you to try gogs, it is very easy to install and maintain,
and its interface is very engaging.  The more gogs users and potential
admins out there, the more comfortable I'll feel making the switch.

-- 
 Bastien

Re: [O] Release 9.0.5

[Bastien Guerry]

Hi Jorge,

Jorge Morais Neto  writes:

> Could we provide an Elisp function to fix this semi-automatically?

I have been affected by this problem too.  I don't have my computer
this week-end, but I'll have a close look on monday.

Thanks,

-- 
 Bastien

Re: [O] Merge 9.0.5 to emacs master?

[Bastien Guerry]

Hi Kyle,

Kyle Meyer  writes:

> Kaushal Modi  writes:
>
>> Kyle -- Would this be a good time to start the merge to emacs master?
>
>>From my standpoint, that'd be fine.  I'm not aware of any outstanding
> patches that need to be backported from the Emacs repo.

Before undertaking this, we need to make sure the Emacs maintainers
are fine with it -- I'm late in reading the related discussions.

Can you wait a few days for my "go" ?

Thanks,

-- 
 Bastien

Re: [O] [RFC] Release Org 9.0 by the end of the next week?

[Bastien Guerry]

Hi Nicolas and Rasmus, 

> Rasmus  writes:
>
>> I have the following patches that I could realistically finish soon:
>
> [...]
>>   - ox-html: move title to preamble for more control over layout/final output
>>   - ox-beamer: more keywords (needs to incorporate Nicolas’ feedback)
>>   - ox-publish: more flexible sitemap

This looks great enhancements, thanks.

> Do you need more time, or can it wait for Org 9.1 ?
>
> If it can wait and there isn't anything blocking left, I think we can go
> ahead and release Org 9.0 very soon.

Agreed.

> Bastien, what date is the most appropriate for you?

The second half of october, I should be able to take half a day for
a quick review and for the release.

Thanks,

-- 
 Bastien

Re: [O] [RFC] Release Org 9.0 by the end of the next week?

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

> If there is no objection, then I suggest to start the release process by
> the end of the next week.
>
> Bastien, do you agree?

Sure I do, no problem.

-- 
 Bastien

Re: [O] bug#24073: 25.1-rc2

[Bastien Guerry]

Nicolas Goaziou  writes:

> This fix looks fine, obviously. You can go ahead as far as Org is
> concerned.

+1

-- 
 Bastien

Re: [O] org.texi edits, patch attached

[Bastien Guerry]

Hi,

Nicolas Goaziou  writes:

> Have you signed FSF papers already? You need to so that we can apply
> your non-trivial changes to documentation.

Yes, Lambda Coder has signed the FSF papers for both Emacs and Tramp.

> You also need to provide a proper commit message, listing sections
> modified in the manual. See commit message in the repo for examples.

Yes, see http://orgmode.org/worg/org-contribute.html#org4682cef for
details on how to write commit messages.

Thanks for the patches!

-- 
 Bastien

[O] org-mode team on gratipay

[Bastien Guerry]

Hi all,

I created a team for org-mode on gratipay.com:

https://gratipay.com/org-mode/

If you are contributing to org-mode, either in core, "contrib/"
or by publishing code related to Org, don't hesitate to join the
team to receive donations.

Thanks!

-- 
 Bastien

Re: [O] bug in org-element--object-lex seen when exporting (Invalid search bound, wrong side of point)

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

> Bastien, I consider this to be a blocking bug for 9.0 release, in case
> your are planning to make the release very soon.

I will of course wait for your "go" and review the major changes
carefully before doing the release.

-- 
 Bastien

[O] [ANN] Emacs workshop in Paris, December 12-13-14

[Bastien Guerry]

Hi all,

I'm giving a 3-days Emacs/Org-mode workshop in Paris on Dec. 12-13-14.

The workshop is in french, and limited to the first four registrants.

Here is an overview of the workshop content:
  http://github.com/bzg/emacs-training

Read more here:
  http://www.2i2l.fr/spip.php?article278

Follow and RT the announcement (in french):
  https://twitter.com/2i2Lformation/status/797096106199044096

I also give individual training online for those interested:
  https://emacs-doctor.com/emacs-training/

Happy hacking!

-- 
 Bastien

[O] Release 9.0.1

[Bastien Guerry]

Hi all,

Org 9.0.1, a bugfix release, is out.

Enjoy!

-- 
 Bastien

Re: [O] Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]

[Bastien Guerry]

Hi,

I changed the order of presentation for installation methods on the
website, promoting Org ELPA method.

Thanks,

-- 
 Bastien

Re: [O] Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]

[Bastien Guerry]

Hi all,

Nicolas Goaziou  writes:

> However, I think we should make more frequent bugfix releases. We may
> even automate such releases, e.g., one week after the last unreleased
> bugfix in the branch. I don't do releases however, so this may just be
> a weird idea.
>
> Bastien, is it even possible?

We could simply have daily snapshot of the maint branch in addition to
daily snapshot of the master branch.

For now http://orgmode.org/org-latest.tar.gz is build from the master
branch, but we could also have http://orgmode.org/org-bugfix.tar.gz.

What do you think?

>> Thought experiment: if it is good enough, surely the web site should
>> point users to this installation method for the stable version?
>
> Isn't it the case already? From the first page I see
>
>   M-x list-packages RET (see Org ELPA)
>
>   Daily snapshots: tar.gz or zip
>
>> I can't imagine there are many users who would prefer to compile from
>> source rather than just use package-install!
>
> I don't think we force users to use development version (even though it
> is appreciated, particularly close to a major release). OTOH, being able
> to browse source code is very important so the "git clone" command and
> the "cgit" link also belong to the first page.

In general, the compiled version is not that much faster and bug
reports we get from uncompiled versions are better.  So it's good
to not force users to use a compiled version IMHO.

>> ​ Also, the version should be the git tag (so that the version number is
>> clearly visible), rather than the current "MMDD" format, which looks
>> like a development snapshot.
>
> We need to tell the difference between a release and a cut from the
> maint branch. 
>
> Also, I'd rather have monotonic version tags, so 8.3.6.whatever is not
> really an option. Maybe 8.3.YYYMMDD... and we drop manual bugfix
> releases altogether.

I'm not sure what is the issue here.

Thanks,

-- 
 Bastien

Re: [O] Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

> I thing we should automate bugfix releases with regular version
> numbering scheme, e.g., 8.3.7 release, /as a replacement for/
> org-MMDD releases.

Okay.

> Therefore:
>
> 1. org-MMDD could be renamed org-MAJOR-MINOR-BUGFIX# where MAJOR
>MINOR are never modified automatically, and BUGFIX# is (1+ last
>BUGFIX#).

I'm fine with this.

> 2. Conditions to make a new automated release ought to change. We could
>wait for a full "idle" week after a commit before releasing (IOW,
>wait for one week after a commit but every new commit during that
>period resets the counter). "next Monday" rule has bitten us already.
>The new rule is not perfect either, but is more secure. If one full
>week is too long, we may reduce it to 4 days.

I'm fine with the rule you suggest.

> OTOH "org-bugfix.tar.gz" is not monotonic, so it buys us very little.

We just need to have a link that I can put on the website without the
need to edit the website for each minor release.

Best,

-- 
 Bastien

Re: [O] Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]

[Bastien Guerry]

Hi,

Reuben Thomas  writes:

> 1. The top heading is "Download and install", but the second half of
> the section is a list of links that look like they belong in a
> different section (List of features, Manuals and tutorials…).

I could not find an elegant solution for this.  I don't have that much
time to dedicate to this, but patches are welcome.

> 2. The various types of download are still too mixed up. For normal
> users, there is no need to offer anything other than the ELPA method
> (unless you think some users still use pre-package.el Emacs?)

I promoted the ELPA version, but I want to allow the download the
archives, as it's still useful, even for normal users.

> I suggest that you move these items to the "Documentation and
> literature" section: Manuals and tutorials, Worg, History &
> acknowledgements, Talks, GSoC.
>
> Remove the heading "Download and install", but instead make the
> entire list heading-sized text. The top-most item in the list should
> be something like:
>
> "Install Org mode from [GNU ELPA]: M-x package-install RET org RET
> (for the [bleeding edge], use [Org ELPA]!)"
>
> The bits in square brackets are links, respectively, to GNU ELPA, the
> bleeding edge Worg page, and the Org ELPA page.
>
> The rest of the list is then:
>
> Mailing list and goodies
> Org tools (outside Emacs)
> How to contribute to Org [no question mark!]
>
> The development version info should move to "How to contribute to
> Org?".

I think the page is fine now -- we can enhance the whole website
at the next big refreshment.

> ​The link to "More on installing Org mode" can be moved to the
> developer documentation.

The links changed -- given that the "Installation instructions" are
often needed, I think it's good to have it here.

> I think this would make the page much easier to parse, and hence
> attract more casual users, as well as saving more experienced users
> time.

Let me know if the current page is at least 90% "good enough" :)

Thanks!

-- 
 Bastien

[O] Release 9.0

[Bastien Guerry]

Hi all,

Org 9.0 is out!  See the release notes here:

http://orgmode.org/Changes.html

Thanks to Nicolas, the non-official but real maintainer
and to all who contributed to this long-awaited release.

As usual, enjoy!

-- 
 Bastien

Re: [O] Org 9.0 out?

[Bastien Guerry]

Hi Kaushal,

Kaushal Modi  writes:

> I just noticed that org 9.0 got released yesterday. I am surprised
> that there was no announcement email.

my bad -- I sent the announcement using my non-gnu email address,
so gmane asked me to confirm while I was alseep.

> Thanks to everyone who contributed to this most awesome org mode
> release!

Indeed, *thanks* to everyone!

-- 
 Bastien

Re: [O] Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]

[Bastien Guerry]

Reuben Thomas  writes:

> Thanks very much for engaging with my criticism to improve things!

Thanks to you for the suggestions!

-- 
 Bastien

Re: [O] allow live execution of code snippets in html export

[Bastien Guerry]

Hi all,

thanks for adding me to this discussion!

klipse + org works pretty much out of the box, which is really great.
I just tested it again with a mix of Scheme and Clojure blocks, both
can work together within the same HTML page.

That said, I think we can take this opportunity to slightly improve
how ox-html handles source code:

- why only  and not  ?

- make src-clojure in  customizable ?

- have ob-javascript.el to let ox-html know how to export js code?

- have org-html-js to easily allow adding js libraries at the bottom
  of a page? Perhaps together with #+html_js and #+html_js_extra ?

>> If the license permits, and there's a precedent, we could bundle the
>> scripts with org.

I have no problem with this, but I'd rather think a more general
mechanism to embed scripts in general and get more flexibility in
css classes.

If we provide a straightforward solution, I don't think there is
a problem pointing to Google servers.

We might have a problem with recommending js code that does not
pass the https://www.gnu.org/software/librejs/ tests: that is,
we cannot recommend code that is not advertised the way librejs
recommends it should be advertized.

This is an annoying issue, but a real one I guess.

As long as Klipse + org is somehow available and documented,
I'll be very happy :)

-- 
 Bastien

Re: [O] [PATCH] allow klipse export in html

[Bastien Guerry]

Hi Matt,

thanks for the new patch!

Before applying it (and working further on it), I suggest we wait for
Yehonathan's feedback on making klipse.js librejs-compatible.  That's
possibly a blocking issue, and we need to sort it out.

Thanks!

-- 
 Bastien

Re: [O] allow live execution of code snippets in html export

[Bastien Guerry]

Hi Matt,

Matt Price  writes:

> Two more little things. HTML blocks can't use the standard editor so
> they need an extra attribute `data-editor-style="html"`

I'm not sure what you mean here: can you give an example?

> Also, it would be nice if klipse had an elisp REPL since so many org
> users blog about elisp.

Seems rather ambitious but I agree this would be fun!

-- 
 Bastien

Re: [O] [PATCH] allow klipse export in html

[Bastien Guerry]

Matt Price  writes:

> And this second patch adds support for html rendering with klipse. 
> The default CSS leaves a little to be desired!

Thanks for both patches -- I think the second one should use
`org-html-klipsify-src' instead of `org-reveal-klipsify-src'
but besides that, I'm pretty sure we cannot link to a js library that
does not pass the js tests.

I will ask on emacs-devel.

Thanks!

-- 
 Bastien

Re: [O] [PATCH] allow klipse export in html

[Bastien Guerry]

Hi Matt,

I finally committed this.  Sorry it took so long and thanks
again for the patch!

Best,

-- 
 Bastien

Re: [O] [PATCH] allow klipse export in html

[Bastien Guerry]

Hi Yehonathan,

Yehonathan Sharvit  writes:

> Good news. Where is the commit?

Here : http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=d5bbf3

-- 
 Bastien

Re: [O] [PATCH] allow klipse export in html

[Bastien Guerry]

Hi Matt,

Matt Price  writes:

> checking again to see if there's any movement on this. I can also
> repatch against master.

well, my bad.  Enough is enough, I will review and commit this today,
sorry for the delay.

-- 
 Bastien

Re: [O] org-plus-contrib, where is library-of-babel.org?

[Bastien Guerry]

Hi Kyle,

Kyle Meyer  writes:

> On the Emacs list, Glenn asked us to add a license to
> library-of-babel.org:
>
> https://lists.gnu.org/archive/html/emacs-devel/2017-07/msg00169.html

thanks for the heads up -- I'm focusing on my work this week and I
won't have time to deal with orgmode requests until this week-end,
but I will then.

> At the time, I wondered whether that file had any contributors without
> copyright assignment.  I briefly looked through the list of authors
> touching library-of-babel.org in the Org repo and the worg repo, and I
> didn't find any contributors that aren't included in the assignment list
> at http://orgmode.org/worg/org-contribute.html

Thanks for checking this.

In general, if some contributors are not listed on org-contribute.html
I can also check on the GNU server for the list of people with copyright
assignment.

I suggest using the same copyright conditions than the one we have for
Worg documentation:

  Documentation from the http://orgmode.org/worg/ website (either in
  its HTML format or in its Org format) is licensed under the GNU Free
  Documentation License version 1.3 or later.  The code examples and
  css stylesheets are licensed under the GNU General Public License v3
  or later.

But: I would first consider whether this file should be part of Emacs
and Org's core.  I think it should be on Worg instead, to get a chance
to be maintained by more contributors.

What do you think?

-- 
 Bastien

Re: [O] org-plus-contrib, where is library-of-babel.org?

[Bastien Guerry]

Kyle Meyer  writes:

>>> Apparently, library-of-babel.org is not distributed with the Org mode
>>> that ships with emacs.  Not sure why that is.  I'm guessing it's a
>>> license issue?
>>
>> It will be in the next release (in /emacs/etc/org/).  If there's a license
>> issue it needs to be removed.

The reason why this library-of-babel.org was not in Emacs is not
because of its lack of license.  I guess it's because Carsten and
Eric didn't think of it as something that should land in Emacs.

Hence my will to clarify this by moving it to Worg, where it will
be more easily accessed.

-- 
 Bastien

Re: [O] Emacs master now updated to Org 9.0.9

[Bastien Guerry]

Indeed, thanks to you and to everyone involved.

I'm very grateful everyone has been patiently baring
with me for this task.

-- 
 Bastien

Re: [O] org mode moves to GNU emacs core

[Bastien Guerry]

Hi Robert,

first of all, my bad: what I should have said in all these discussion
is that any decision regarding moving Org to Emacs' core won't happen
any time soon (I'd say two or three years).

Keeping Emacs master branch in sync with Org maint branch is not a
problem anymore, so the decision of whether Org should go into Emacs
core will not depend on this.

And by the time the decision will be made, I expect Emacs and Org
release cycles will come close.  In other words: when Org will be as
stable as Emacs and when most of Org's development will happen in its
external modules, it will be time to move Org's development to Emacs.

But all this is very hypothetical, right now very much "bikeshed" :)

Best,

-- 
 Bastien

Re: [O] org mode moves to GNU emacs core

[Bastien Guerry]

Hi Philip,

phillip.l...@russet.org.uk (Phillip Lord) writes:

> I presume you do see this as an advantage? The issue is, surely,
> that it's too much of a PITA for the advantage that you gain?

Well, it's not really about PITA-or-not-PITA, it's just that I want
org-mode to be the default mode for some files in Emacs, and having
org-mode in Emacs' core is the most simple way to go for this.

Maintainers of projects like Gnus or CEDET don't want their code to
live outside of Emacs repo neither, so I guess simplicity is a big
win.

-- 
 Bastien

Re: [O] org-plus-contrib, where is library-of-babel.org?

[Bastien Guerry]

Hi Kyle,

the library of Babel now lives in Worg here:
http://orgmode.org/worg/library-of-babel.html

I’ve checked and fixed references to it in Org’s documentation,
but if I missed something please let me know.

Thanks,

-- 
 Bastien

Re: [O] [PATCH] doc/Makefile: Auto-generate org-version.tex for orgcard

[Bastien Guerry]

Hi Kyle,

Kyle Meyer  writes:

> It seems that the only place where we hardcode the Org version is
> orgcard.tex.  Any objections to auto-generating this as well?

None from me, thanks for this.

-- 
 Bastien

Re: [O] Capture template stopped working: nil

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

>> What is the reason for this change?
>
> I don't like `eval' in the code base.

May I ask you why `eval' in the code base is problematic?

This change may break current configurations.  Such changes should
be made with extreme parcimony and for very consensual reasons.

-- 
 Bastien

Re: [O] Backward incompatible outline-invisible-p change in emacs master for Org

[Bastien Guerry]

Hi Paul,

thanks for the follow-up -- Kaushal, thanks for the fix, please go
ahead and commit it.

Best,

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

Hi,

if you need commit access to org-mode to add code to contrib/,
please send me your public key (the one in ~/.ssh/id...).

Best,

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

"numbch...@gmail.com"  writes:

> Here is the patch

The patch needs to have a proper changelog.  You can read
http://orgmode.org/worg/org-contribute.html#patches carefully
for details.

Thanks!

-- 
 Bastien

Re: [O] Backward incompatible outline-invisible-p change in emacs master for Org

[Bastien Guerry]

Kaushal Modi  writes:

> Before I commit this to master, I was thinking that this patch looks
> safe enough for the maint branch. If there are no objections, I can
> commit this to maint and merge to master.

Sure, please go ahead.

Thanks!

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

"numbch...@gmail.com"  writes:

> Sorry, update SSH public key:

Please resend it as an attachment in a private email.

Thanks,

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

"numbch...@gmail.com"  writes:

> Did my SSH public key add to org-mode repository?

Now yes.

You first need to pull org-mode again like this:

~$ git clone orgm...@orgmode.org:org-mode.git

Then you will be able to push commits.

Do not commit changes outside of the contrib/ repository.

If you have signed the FSF copyright papers, please let me
know under what name.

Best,

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

Applied, thanks!

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

> I'm not sure to understand commit
> a023d670eceb9121ef6a511b108fd82265e6d6a8.  In particular, why did
> you remove lexical binding? It really should be active in every
> library, and is the default when you create a new one.

I didn't know lexical binding was now the default when creating a
library.

Still: when it is not used, why adding it?

-- 
 Bastien

Re: [O] Backward incompatible outline-invisible-p change in emacs master for Org

[Bastien Guerry]

Hi Kaushal,

thanks for putting me in the loop.

Kaushal Modi  writes:

> I also find an org-invisible-p2 function, but it's not clear why it
> does a (backward-char  1) before doing invisibility check.. and that
> too eventually relies on outline-visible-p. (Turns out this function
> has a long history: http://orgmode.org/cgit.cgi/org-mode.git/commit/?
> id=93a4128a6fe47b4e05c0a7cb3ec14878b41d6000 )

The question is: why this patch in the first place?  Paul authored it
and I committed it, so I should know--but I don't.  Maybe Paul know or
you know better?

> Here's a patch for the above proposed solution.

This looks fine, but I'd rather revert the faulty Emacs commit if
it is not necessary.

Until Paul enlighten us, I'll have a deeper look.

Thanks,

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou  writes:

> There is absolutely no drawback in using lexical binding. Since Emacs
> 24.1, it _is_ the default for Elisp: every Elisp file created activates
> it, the other binding being for compatibility with older libraries.

Maybe I miss something: when I create a file with C-x C-f whatever.el RET
it does not use a template or does not get created with lexical binding on.

What are you referring to when you say "every Elisp file created activates it"?

> Please, pretty please, don't suggest it is different.

Quoting the Emacs Lisp manual:

  This is the ‘GNU Emacs Lisp Reference Manual’ corresponding to Emacs
  version 26.0.50.

  ...

  Scoping Rules for Variable Bindings

  * Dynamic Binding:: The default for binding local variables in Emacs.
  * Dynamic Binding Tips::Avoiding problems with dynamic binding.
  * Lexical Binding:: A different type of local variable binding.

  ...

  12.10.1 Dynamic Binding
  ---
  
  By default, the local variable bindings made by Emacs are dynamic
  bindings.  When a variable is dynamically bound, its current binding at
  any point in the execution of the Lisp program is simply the most
  recently-created dynamic local binding for that symbol, or the global
  binding if there is no such local binding.

To me the manual clearly says dynamic binding is the default, and
that's why using lexical binding requires additional info in the file.

Whether lexical binding is a good default or not is another question,
and whether lexical-binding:t makes sense in a file with no binding
yet another, third one.

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

Hi Nicolas,

Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:

> Bastien Guerry <b...@gnu.org> writes:
>
>> Still: when it is not used, why adding it?
>
> We are not adding it since it is in the file by default; you removed
> it :)

I guess it is in the file by default because the odds are good that
lexical scoping will be actually used.

> This is an odd question, however. The thing is: how is Emacs-lisp
> scoping, dynamic or lexical? We ought not consider it to be both
> throughout the code base (even though one file still uses dynamic
> scoping) as it is just confusing for developers. Since lexical scoping
> prevents a whole class of (vicious) bugs, it is the most common type of
> scoping among modern languages, by large. As of Emacs 24.1, let's just
> consider Elisp to be lexically scoped.

I agree it's good to have lexical scoping, but I don't consider Elisp
to be lexical scopped -- I consider Elisp to let the user pick up the
constraints he wants, with dynamic binding still being the default.

> In a nutshell, "-*- lexical-binding:t ; -*-" ought to be a mandatory
> cookie in every Elisp file.

Maybe lexical binding will be the default behavior one day, but in the
meantime, I would suggest to use "-*- lexical-binding:t ; -*-" only if
lexical binding is actually used in the file.

Best,

-- 
 Bastien

Re: [O] Add ob-sclang.el for sclang Org-mode babel support in contrib/

[Bastien Guerry]

Hi Nicolas,

I'm all for lexical-binding, and it's good to have it in Org's core.

The author of ob-sclang.el used "2011-2017" for the copyright years,
which was obviously a typo and tells that the header was simply copied
from another file (which is 100% fine btw).

>From that, I inferred that the "lexical-binding:t" was also copied
without further thinking, especially since there is no binding at all
in this file.

I think Stardiviner is the one who should make the decision, but I
don't see what "lexical-binding:t" would add to his actual code.

For the more general concern: again, I'm all for lexical binding and
I'm well aware of its numerous advantages, but I don't think we should
rule dynamic binding from contributed Org code.  Dynamic binding has
it's limitations, but when used carefully, it also has the advantage
of being easier to grok for beginners.  We want to welcome beginner's
contributions.  So I simply recommand lexical binding for Org's core,
and what fits developers best for Org's contributions.

And I agree we can move on to something else :)

-- 
 Bastien

Re: [O] Release 9.1.2

[Bastien Guerry]

Hi,

"Cook, Malcolm"  writes:

> Should we expect to find release notes at
> http://orgmode.org/Changes.html or somewhere else?

Yes, that's the place for human readable changelogs, which we update
for major and minor releases, not for bugfix releases.

And http://orgmode.org/cgit.cgi/org-mode.git/log/ gives the detailed
git logs.

HTH,

-- 
 Bastien

Re: [O] mimetype for orgmode files

[Bastien Guerry]

Hi Yasushi,

Yasushi SHOJI  writes:

> There is RFC 6648, which "deprecating the "X-" Prefix".

Thanks for letting us know!

> So, it might be better to use "text/org".

I’m fine with "text/org".  John?  Others?

I’ll make the change later this week if nobody disagrees.

Thanks,

-- 
 Bastien

[O] Release Org 9.0.10

[Bastien Guerry]

Hi all,

Org 9.0.10 is out, the last bugfix release before 9.1,
which is to be released next week.

Thanks to everyone involved!

-- 
 Bastien

Re: [O] Release Org 9.1 soon ?

[Bastien Guerry]

Hi Nicolas,

I’m just back from vacation.

Nicolas Goaziou  writes:

> I think it would be good to release Org 9.1 before the end of the month,
> if possible.

Yes, that’s a good date.

> Is there any major issue left, or any important pending patch to apply
> before doing the merge?

I’ll have a look today and tomorrow and let you know if there is
something on my side.

> Once this is done, I will merge the "hide-column" branch in master.

Thanks.

> I will also take care of removing Org Struct mode from the code
> base.

What are the good alternatives?

Even if the functionality is buggy and the implementation hugly, some
users may still find it useful, we need to take care of providing good
alternatives.

-- 
 Bastien

Re: [O] Release Org 9.1 soon ?

[Bastien Guerry]

Hi Kaushal and Nicolas,

Nicolas Goaziou  writes:

> There's no hurry anyways. I don't consider this to be a blocker for Org
> 9.1. Of course, it is better if it can be integrated before.

If org-set-tags is to be rewritten, we need to carefully test the
rewrite before integrating it.  So 9.2 is a decent goal for it,
assuming 9.2 will be closer to 9.1 than 9.1 to 9.0.

> Please do, but first, why do you think it is better to have it in core
> instead of, e.g., GNU Elpa? Doesn't "ox-publish" provide some static
> site generation features already?
>
> Also, "ox-hugo" requires "ox-blackfriday", which is another Markdown
> back-end. I'm not questioning the usefulness of this package, but
> I think we need very good reasons to provide overlapping features out of
> the box.

Indeed.  Again, the biggest issue here is that of discoverability,
and moving code into core is the simplest way, but not necessarily
the better.  We can expect new exporters to live in GNU ELPA (or
elsewhere) first, then to be included in core is there is a strong
support and a strong need for it.

-- 
 Bastien

Re: [O] Scheme output results

[Bastien Guerry]

Hi Neil,

Nicolas Goaziou  writes:

> I cannot, I'm not the maintainer. I'm Cc'ing Bastien. I'll apply your
> patch as soon as it is sorted out.

Thanks for contributing.

I’ve found your copyright assignment for GUILE but it does not cover
changes for GNU Emacs, you would need another copyright assignment for
this.

Thanks in advance,

-- 
 Bastien

Re: [O] Release Org 9.1 soon ?

[Bastien Guerry]

Hi Kaushal,

Kaushal Modi  writes:

> I'd also like to add a new Org exporter, ox-hugo. As adding it
> wouldn't break other Org functionality, would it be safe to add it
> before this master cut? About this, would it be OK to start by
> creating a scratch branch?

no problem at all for creating a Scratch branch for any purpose in
general, but please wait before adding more exporters.

I would like to set up something like https://gogs.io on the server
to move the code in contribs/ outside of Org’s repo, and to be more
conservative on what’s goes in Org’s core.

I plan to do this move in the next coming weeks, and to discuss it
on the mailing list precisely before, of course.

Thanks,

-- 
 Bastien