[O] Release 9.1.13

[Bastien]

Hi all,

Org 9.1.13, a quick bugfix release, it out.

Enjoy!

-- 
 Bastien

[O] [BUG] ox-html's klipse has problem with org-info.js

[stardiviner]

In a simple klipse test by N. Raghavendra (thanks) is at here:
http://www.retrotexts.net/tmp/ox-html-klipse/

It works fine.

But when I add `(org-html-use-infojs t)` into `EMACS=` code's let-binding.

klipse has problem.

Can't find out the bug, because I don't know JavaScript.

Is there someone can fix it?

-- 
[ stardiviner ] don't need to convince with trends.
   Blog: https://stardiviner.github.io/
   IRC(freenode): stardiviner
   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
  

Re: [O] How to use ox-html klipse in org-publish?

[stardiviner]

Hi, N. Raghavendra, follow your Makefile and Org test file. I run on my
machine, klipse works fine. This must be problem on my configuration. I
will find it out. Really thanks for your help.

--
[ stardiviner ] don't need to convince with trends.
   Blog: https://stardiviner.github.io/
   IRC(freenode): stardiviner
   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Carsten Dominik]

On Sat, May 5, 2018 at 8:02 PM Rasmus  wrote:

> Nicolas Goaziou  writes:
>
> > Hello,
> >
> > Steve Downey  writes:
> >
> >> Asking users to accept any breakage in the tool they use to get work
> done
> >> is a lot. Changes in UI in emacs are opt-in.
> >>
> >> Even if the change is the right thing to do.
> >
> > I think some of you (basically, anyone thinking we should enable " > TAB" by default ;)) are missing the point.
> >
> >
> > The first important thing to understand is that, even if we enable
> > `org-tempo' by default, next Org release /will break/ for some of us.
> >
> > - It will break because `org-tempo' is only 99% backward-compatible.  So
> >   anyone having customizing templates is bound to change them.
> >
> > - It will break because there are 9 other incompatible changes between
> >   9.1 and 9.2.
> >
> > So, asking to load `org-tempo' by default just to avoid breaking users
> > set-up is a wrong argument. It will only "protect" those among us that
> > use " > incompatible changes. IOW, updating Org from 9.1 to 9.2 will not be
> > smooth for everyone. No matter what `org-tempo' becomes.
>
> Nicolas, I have been wondering about something, reading all these posts,
> irrespective of whether tempo is loaded by default or not (I don’t care).
>
> Do you think org-tempo should try to detect "old" versions of
> org-structure-template-alist and give a better error if it sees one?  I
> don’t know what the "best practice" is this case...
>

Yes, it absolutely should.

Carsten


>
> Thanks,
> Rasmus
>
> --
> When in doubt, do it!
>
>
>

Re: [O] Orgalist notes

[Eric Abrahamsen]

Nicolas Goaziou  writes:

> Hello,
>
> Gregor Zattler  writes:
>
>> Hi Eric, orgalist users,
>> * Eric Abrahamsen  [2018-05-03; 23:45]:
>>> Huh! I tried the exact same typing as you've done above, and the third
>>>  item wraps into a fourth item. I expect it will be some interaction
>>>  with other minor modes. I've got:
>>
>> I have the very same problems with unstoppable indentation in
>>   orgalist and I don't think it is an interaction with other
>>   minor modes, because it hits even with no configuration.  Do:
>>
>> emacs25 -Q  --debug-init  -l 
>> /home/grfz/.emacs.d/elpa-27.0/orgalist-1.3/orgalist.el   -f compose-mail 
>> --eval "(progn (orgalist-mode t) (end-of-buffer) (newline) (newline))"
>>
>> (you'll have to adjust the path to your orglist.el)
>>
>> and hit RETURN in the newly created emacs frame and this last new
>> line will be indented.
>>
>>
>> I also tested with a freshly build emacs from the master branch
>>   and it showed the same behaviour.
>
> Indeed. When I tried make Orgalist mode fair with other minor modes and
> switched to using advices, I encountered a few unexpected hiccups, most
> notably bug#31361, which is responsible for some erratic indentation.
>
> I eventually worked around it, and just updated Orgalist. It should be
> available on ELPA toworrow. Hopefully, thing will become a bit smoother.
>
> Thank you for the reports.
>
> Regards,

And, as always, thank you! This is fairly heroic work -- I say that
after having made an attempt at orgstruct-mode, and run away screaming.
And look, no funny indentation!

- Yet a list item with a ridiculous amount of text in it does not wrap
  into a second list item.
- Neither does the second list item, despite having an equivalent amount
  of spurious typing in it.

- And before I get tired of the experiment, here's the same thing with
 a numbered list.
- Oh damn, I hit M-RET, and the numbered list turned into an unnumbered
  list.

No good deed goes unpunished :)

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Josiah Schwab]

On  5 May 2018 at 16:26 PDT, Adrian Bradd wrote:

>> I remember that Magit experimented displaying a message the first
>> time you used a new release; you would silence it only by setting a
>> variable.  I don't think this is the case anymore, so it may have
>> failed, though.
>
> I believe this was for the Magit Kickstarter fundraiser. A message was
> displayed to notify users and direct them to the page.

No, I believe what was being referenced was this:

  https://github.com/magit/magit/issues/1803

Josiah

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Adrian Bradd]

I remember that Magit experimented displaying a message the 
first time
you used a new release; you would silence it only by setting a 
variable.
I don't think this is the case anymore, so it may have failed, 
though.


I believe this was for the Magit Kickstarter fundraiser. A message 
was displayed to notify users and direct them to the page. This 
message stayed in place until the Kickstarter was completed, but 
could be disabled prematurely by altering a variable. I can't 
speak to its success or failure overall, but there were some 
complaints about the method [1].


We could also make the  page 
more

prominent in the summary displayed along with the package.


This seems like a step in the right direction. Perhaps adding a 
section to the Introduction in the manual about the changes page 
or ORG-NEWS and their importance with major or .X releases might 
help.


My experience as a newcomer to org with the 8.x to 9.x transition 
was that most of the posts relating to org at the time (on reddit 
at least) mentioned breaking changes and the ORG-NEWS file.


With regard to the poll, I don't have a strong opinion as I am now 
using yasnippet with org. When I was using org-tempo I didn't see 
any issue with having to require it in my init. So I suppose my 
vote would be that disabling by default is 
fine. `org-insert-structure-template' bound to a key seems like a 
reasonable alternative especially since it operates on regions.


Cheers,

[1] https://github.com/magit/magit/issues/3174

--
Adrian

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Rasmus]

Aaron Ecay  writes:

>> Expansion templates are a great thing, but this is only sugar for Org,
>> which is totally usable without them. Besides, some facilities are
>> providing it for us. This falls into (2). By design, I'm convinced we
>> should not include them. I also wish that anyone involved in this thread
>> can take a step back to see the whole picture.
>
> This is a red herring.  The changes do not eliminate expansion template
> code from org.  They merely substitute (incompatibly) one expansion
> template mechanism for a new one.
>
> FWIW, I do think the idea is worth exploring of getting rid of the (old
> and new) template expansion code and using emacsʼs built-in SRecode
> template facility.  Like most of the CEDET stuff, it looks horridly
> overengineered at a first glance.  But it is also included with emacs by
> default (unlike e.g. yasnippet which otherwise looks more pleasant to
> program to me), and it would be (even more) responsive to the concerns
> from emacs-devel that were quoted in your full message.  To be specific,
> this would entail (eventually) getting rid of the
> org-structure-template-alist variable entirely, as well as the menu now
> bound to C-c C-,; the former would be replaced by (AFAIUI) template
> files that would be included with org and/or created by users for their
> custom templates; the latter would use SRecodeʼs built-in template
> selection instead.


Cool, I at least did not know that one.
Can you a reproducible way to try it out?
Without having to make my own templates etc.

Rasmus

-- 
Not everything that goes around comes back around, you know

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Rasmus]

Nicolas Goaziou  writes:

> Hello,
>
> Steve Downey  writes:
>
>> Asking users to accept any breakage in the tool they use to get work done
>> is a lot. Changes in UI in emacs are opt-in.
>>
>> Even if the change is the right thing to do.
>
> I think some of you (basically, anyone thinking we should enable " TAB" by default ;)) are missing the point.
>
>
> The first important thing to understand is that, even if we enable
> `org-tempo' by default, next Org release /will break/ for some of us.
>
> - It will break because `org-tempo' is only 99% backward-compatible.  So
>   anyone having customizing templates is bound to change them.
>
> - It will break because there are 9 other incompatible changes between
>   9.1 and 9.2.
>
> So, asking to load `org-tempo' by default just to avoid breaking users
> set-up is a wrong argument. It will only "protect" those among us that
> use " incompatible changes. IOW, updating Org from 9.1 to 9.2 will not be
> smooth for everyone. No matter what `org-tempo' becomes.

Nicolas, I have been wondering about something, reading all these posts,
irrespective of whether tempo is loaded by default or not (I don’t care).

Do you think org-tempo should try to detect "old" versions of
org-structure-template-alist and give a better error if it sees one?  I
don’t know what the "best practice" is this case...

Thanks,
Rasmus

-- 
When in doubt, do it!

Re: [O] Moving from Jekyll to Orgmode

[Rasmus]

ST  writes:

> Hello,
>
> I would like to rewrite my website using Orgmode (till now I used
> Jekyll). It would be nice if you could help me with following questions:
>
> 1. could somebody, please, point me to a tutorial on how to create a
> multilingual site? Like the orgmode.org with EN:FR:JA. Ideally it would
> be if one would have page-aware language switch, i.e. if one is on the
> page orgmode.org/fr/features.html and clicks JA he will be redirected to
> orgmode.org/ja/features.html (and not .../ja/index.html as it is now)...

I don’t know how to that.  You can easily add language buttons to your
documents via :html-preamble (see org-publish-project-alist).  How to
automatically move people to the right side based on their preferences is
another thing.  I know Django supports multilingual pages, so maybe their
documentation discuss this issue on a more technical level.

> 2. how can one create "prettified" links, i.e. /features/ instead
> of /features.html ? Basically during the website generation for the file
> features.org a directory `features` needs to be created and the html
> file placed into `features/index.html` ... Is there a tutorial on how to
> do that?

You make a wrapper around org-html-publish-to-html that creates folders
and from filename and save file as index in the folder.  The wrapper
function is then used as the :publishing-function in
org-publish-project-alist.

Something like this (untested).

(lambda (plist filename pub-dir)
  (let ((dir (make-directory (file-name-as-directory (file-name-base filename))
 pub-dir)))
(org-latex-publish-to-html plist filename dir)
(rename-file (concat dir (file-name-base filename) ".html")
 (concat dir "index.html"


You could also move around your source files before publishing via the
:preparation-function.

> 3. is there a free modern "corporate" style theme for org-mode?

Everything has classes so it’s easy to make a style that suits you.  Just
find the color and font combinations that you like.

There’s an example of a technique I use here:

https://gitlab.com/pages/org-mode

Rasmus

-- 
Look, it is what it is because it was what it was

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Rasmus]

Tim Cross  writes:

> won't that conflict with the key binding for block editing mode?

Isn’t that "C-’".  Blocks are "C-c C-,".  I used some program to scavenge
for unused bindings in, I think, December last year and we discussed it on
the list.  I think the main contenders were "C-c C-." and "C-c C-," and
the latter is a bit nicer on my keyboard layout...
 
I might be have misunderstood something, if so I apologize.

> Also, I think C-c , is possibly more in-line with other
> template/expansion commands in other modes.

Don’t know.  Why?

Rasmus

-- 
Er du tosset for noge' lårt!

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Rasmus]

Aaron Ecay  writes:

> Hi Rasmus,
>
> 2018ko maiatzak 2an, Rasmus Pank Roulund-ek idatzi zuen:
>>> Finally, irrespective of which options are chosen, I think that org-tempo
>>> would be better implemented in terms of a minor mode.  This would allow
>>> it to be autoloaded, turned on/off for different buffer(s) in an emacs
>>> session, and avoid duplicating the logic for activating global minor
>>> modes.  Patch attached.
>> 
>> I agree.
>
> OK, thatʼs good to know.  Iʼve held off on any pushing of the patch to
> master until everything is worked out.  In the meantime, Iʼve put it in
> a branch “org-tempo”.
>
> I also added a second commit to that branch which implements my vision
> of the upgrade path (deprecation warnings, etc.)  For convenience, that
> patch is also attached to this email.

I don’t like it, I’m afraid.  It’s a bit nagging.  There’s tools to mark
thinks as obsolete in Emacs should we need to.

> One remaining decision to make is: what is the future of org-tempo?  I am
> sympathetic to the idea that the best place for it eventually would be
> org-contrib or GNU ELPA, and not org core.

We don’t have make that decision now, do we?

Rasmus

-- 
This message is brought to you by the department of redundant departments

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Rasmus]

Kevin Foley  writes:

> Bastien  writes:
>
> I have to admit that Bastien's list describes my experience almost
> perfectly.  It look me a long time to figure out something that in the end
> seemed very simple.  At the time I wasn't familiar with the NEWS file and
> it didn't come up in any of my online searches.  It also didn't help that
> site still documented the old behavior (and apparently still does
> https://orgmode.org/manual/Easy-templates.html).

AFAIK the maint manual is published online.

Rasmus

-- 
The right to be left alone is a human right

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Rasmus]

Bastien  writes:

> Hi Tim,
>
> thanks for your thorough and balanced feedback.
>
> Tim Cross  writes:
>
>> There is no solution which will make everyone happy. However, as a long
>> term org user who hopes to continue using org for many more years, I
>> tend to come down on the side of whatever will make org easier to
>> maintain in the long term.
>
> For org-tempo, Rasmus wrote it so I'm inclined to listen quite
> carefully at his opinion.

Please don’t.  I have not really made any policy decisions of sort.  I
only missed " ... 
> In fact, I'm inclined to ask the real question: if org-tempo is on by
> default, who will have good reasons to turn it off and why?

I certainly won’t be :)

Rasmus

-- 
However beautiful the theory, one should occasionally look at the evidence

Re: [O] How to use ox-html klipse in org-publish?

[N. Raghavendra]

At 2018-05-05T21:46:05+08:00, stardiviner wrote:

> But my org-publish result does not see kipse result
> https://stardiviner.github.io/Blog/2016-04-22%2022:54.html#org6921533.
>
> The exported page should like this:
> http://blog.klipse.tech//omnibus/2017/04/23/omnibus-1-wallpaper.html
> Is there anybody using this klipse feature in exporting/publishing?
> Can you give me some hints or show me your configuration about how ?

I don't use klipse, but have checked just now that it works.  Please see

http://www.retrotexts.net/tmp/ox-html-klipse/klipse.html

1. If you type

http://www.gnu.org/;>The GNU project

below the `span' element in the HTML section, you should see a link to
the GNU Web site below "Hello, world!".

2. If you type

(list-of-squares 10)

below the definition in the Scheme section, you should see

(0 1 4 9 16 25 36 49 64 81 100)

at the bottom.

3. The Org file and the Makefile that generated the HTML are at

http://www.retrotexts.net/tmp/ox-html-klipse/

in case you want to see them.

I hope this helps.

Best regards,
Raghu.

--
N. Raghavendra , http://www.retrotexts.net/
Harish-Chandra Research Institute, http://www.hri.res.in/

[O] How to use ox-html klipse in org-publish?

[stardiviner]

I try to use:

,
| (setq org-html-klipsify-src t)

| and

| (setq org-publish-project-alist
|   (...
|   :html-klipsify-src t
|   ...
|   ))
`

But my org-publish result does not see kipse result
https://stardiviner.github.io/Blog/2016-04-22%2022:54.html#org6921533.

The exported page should like this:
http://blog.klipse.tech//omnibus/2017/04/23/omnibus-1-wallpaper.html

Is there anybody using this klipse feature in exporting/publishing?
Can you give me some hints or show me your configuration about how ?

Thanks in advance.

--
[ stardiviner ] don't need to convince with trends.
   Blog: https://stardiviner.github.io/
   IRC(freenode): stardiviner
   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

Re: [O] Orgalist notes

[Nicolas Goaziou]

Hello,

Gregor Zattler  writes:

> Hi Eric, orgalist users,
> * Eric Abrahamsen  [2018-05-03; 23:45]:
>> Huh! I tried the exact same typing as you've done above, and the third
>>  item wraps into a fourth item. I expect it will be some interaction
>>  with other minor modes. I've got:
>
> I have the very same problems with unstoppable indentation in
>   orgalist and I don't think it is an interaction with other
>   minor modes, because it hits even with no configuration.  Do:
>
> emacs25 -Q  --debug-init  -l 
> /home/grfz/.emacs.d/elpa-27.0/orgalist-1.3/orgalist.el   -f compose-mail 
> --eval "(progn (orgalist-mode t) (end-of-buffer) (newline) (newline))"
>
> (you'll have to adjust the path to your orglist.el)
>
> and hit RETURN in the newly created emacs frame and this last new
> line will be indented.
>
>
> I also tested with a freshly build emacs from the master branch
>   and it showed the same behaviour.

Indeed. When I tried make Orgalist mode fair with other minor modes and
switched to using advices, I encountered a few unexpected hiccups, most
notably bug#31361, which is responsible for some erratic indentation.

I eventually worked around it, and just updated Orgalist. It should be
available on ELPA toworrow. Hopefully, thing will become a bit smoother.

Thank you for the reports.

Regards,

-- 
Nicolas Goaziou

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

[Nicolas Goaziou]

Hello,

Tim Cross  writes:

> The C-c , binding is in line with expansion/templates in other modes (at
> least in my configuration), so there is little cognitive overhead when I
> want to expand "something".

`C-c ,' is a keybinding reserved for minor modes. See (info "(elisp) Key
Binding Conventions")

We should avoid, if possible, to use it.

Regards,

-- 
Nicolas Goaziou

Re: [O] Orgalist notes

[Gregor Zattler]

Hi Eric, orgalist users,
* Eric Abrahamsen  [2018-05-03; 23:45]:
> Huh! I tried the exact same typing as you've done above, and the third
>  item wraps into a fourth item. I expect it will be some interaction
>  with other minor modes. I've got:

I have the very same problems with unstoppable indentation in
  orgalist and I don't think it is an interaction with other
  minor modes, because it hits even with no configuration.  Do:

emacs25 -Q  --debug-init  -l 
/home/grfz/.emacs.d/elpa-27.0/orgalist-1.3/orgalist.el   -f compose-mail --eval 
"(progn (orgalist-mode t) (end-of-buffer) (newline) (newline))"

(you'll have to adjust the path to your orglist.el)

and hit RETURN in the newly created emacs frame and this last new
line will be indented.


I also tested with a freshly build emacs from the master branch
  and it showed the same behaviour.


Ciao; Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

[O] Org-mode pcomplete is slow, affect performance

[stardiviner]

I use Emacs profiler profiled company-capf in Org-mode buffer.
Here is an org-mode buffer test snippet (in a big Org file):

#+begin_src clojure :results pp
(nth '(1 2 3) 1)
#+end_src

Profiler result in attachments. It has very recursive deep file-truename
invoking.

+ command-execute4769  56%
- company-post-command   1645  19%
 - company--perform  1555  18%
  - company--continue1539  18%
   - company-calculate-candidates1539  18%
- company--postprocess-candidates1536  18%
 - company--transform-candidates 1536  18%
  - company-sort-by-occurrence   1536  18%
   - cl-delete-if1536  18%
- apply  1536  18%
 - cl-delete 1536  18%
  - #1536  18%
   - company--occurrence-predicate   1523  18%
- company-call-backend   1519  17%
 - company--force-sync   1519  17%
  - apply1519  17%
   - company-call-backend-raw1519  17%
- apply  1519  17%
 - company-capf  1516  17%
  - company--capf-data   1513  17%
   - company--capf-data-real 1513  17%
- run-hook-wrapped   1513  17%
 - completion--capf-wrapper  1513  17%
  - pcomplete-completions-at-point   1510  17%
   - pcomplete-completions   1203  14%
- pcomplete/org-mode/block-option/src   
1160  13%
 - pcomplete--here593   7%
  - file-truename 590   6%
   - file-truename543   6%
- file-truename   455   5%
 - file-truename  409   4%
  - file-truename 355   4%
   - file-truename281   3%
- file-truename   213   2%
 - file-truename  186   2%
  - file-truename 149   1%
   - file-truename109   1%
- file-truename 67   0%
   file-truename 25   0%
 + while  564   6%
+ pcomplete-parse-arguments 25   0%
+ org-command-at-point 18   0%
   + mapcar   283   3%
   + comint--unquote-argument   7   0%
 pcomplete--common-suffix   7   0%
+ derived-mode-p4   0%
+ company--fetch-candidates 3   0%
  + company-call-frontends 16   0%
 + company-call-frontends  90   1%
- ...1451  17%
 - company-auto-begin 954  11%
  - company--perform  954  11%
   - company--begin-new   954  11%
- company-call-backend941  11%
 - company--force-sync941  11%
  - apply 941  11%
   - company-call-backend-raw 941  11%
- apply   941  11%
 - company-capf   941  11%
  - company--capf-data938  11%
   - company--capf-data-real  938  11%
- run-hook-wrapped938  11%
 - completion--capf-wrapper   938  11%
 

Re: [O] [SOLVED] org-attach provide org-store-link like link for org-insert-link

[tumashu]

At 2018-05-05 13:14:10, "stardiviner"  wrote:
>
>stardiviner  writes:
>
>> I used a lot with org-attach to insert files like images, small PDF
>> files, and audio. Every time I attached one file, I have to manually
>> link to that attachment file.
>>
>> Can org-attach provide link directly after finished attaching? So user
>> can press [C-c C-l] (org-insert-link) directly.
>
>After check out org-attach.el source code. I found option
>`org-attach-store-link-p`. This is what I want.

A very good tip, thanks!
>
>--
>[ stardiviner ] don't need to convince with trends.
>   Blog: https://stardiviner.github.io/
>   IRC(freenode): stardiviner
>   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

[O] org-indent-mode and wrapping of bullet

[Michael Brand]

Hi all

When an item or heading with a single word is wider than the buffer
width it is shown as

│-│
│http://www.orgmode.org/z\│
│zzz  │
│*│
│http://www.orgmode.org/z\│
│zzz  │

when not in org-indent-mode which I understand from a
wrapping-code-complexity view. But in org-indent-mode the word is
still on its own line

│-│
│  http://www.orgmode.org/zzz\│
│  z  │
│*│
│  http://www.orgmode.org/zzz\│
│  z  │

where I expect the much nicer looking and space saving

│- http://www.orgmode.org/zzz\│
│  z  │
│* http://www.orgmode.org/zzz\│
│  z  │

Is this a missing feature of org-indent-mode?

Michael

Re: [O] how to use org-crypt with different key per file or node?

[stardiviner]

Can let this property CRYPTKEY support interactive select keys from minibuffer?

Manully input is not an good choice obviously.

How to let org-mode property auto prompt for a list of keys after
inserted property key "CRYPTKEY"?

--
[ stardiviner ] don't need to convince with trends.
   Blog: https://stardiviner.github.io/
   IRC(freenode): stardiviner
   GPG: F09F650D7D674819892591401B5DF1C95AE89AC3