Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-18 Thread Bernt Hansen
Nick Dokos  writes:

> Adam Porter  writes:
>
>> I'm not an expert on this package nor this situation, however, looking
>> at the htmlize.el file shows:
>>
>> ;; Copyright (C) 1997-2003,2005,2006,2009,2011,2012,2014,2017,2018
>>
>> So it would appear that the package has existed longer than either
>> GitHub or Org.  I'm guessing that its author moved its primary repo to
>> GitHub after Org started using it.
>>
>> In hindsight, perhaps it would have been better to move htmlize into
>> Emacs before adding it to Org proper.  But many things are clearer in
>> hindsight.
>>
>> Regardless of where it is hosted, htmlize.el is Free Software, and it's
>> an optional addon to Org.  We can encourage its author to add it to
>> Emacs proper, or to ELPA.  But surely it's not necessary to censor the
>> mention of "GitHub" in the manual; it's simply a fact that GitHub exists
>> and that htmlize.el is currently hosted there.  It would seem
>> unreasonable for the Org maintainers to have reacted to htmlize.el's
>> moving to GitHub by removing htmlize.el support while it remains Free
>> Software, yet that's the logical conclusion of this argument.
>>
>
> I had exactly the same reaction.

Me too!

>
>> So please do not remove support for this package because of where its
>> repo happens to be hosted at the moment.  That would be a major
>> regression, and it would not be in users' best interests.  It would not
>> be fair to remove a major feature used by thousands of users and demand
>> that "someone" (since there is no one ultimately responsible) rewrite
>> large parts of ox-html.el to fix it.  It would at least seem fair for
>> those insisting on the change to do the necessary work.
>>
>
> I don't usually +1 replies but I wanted to chime in my agreement with
> Adam here.  Thanks for taking the time to put your (and my!) thoughts
> into words.
>
> If Github is indeed the sticking point, why can't it (the htmlize
> repo) be cloned on the same server as org-mode (possibly as its own
> repo, possibly as a git submodule)? It's not a fast moving target: a
> handful or two of commits per year. The doc can then avoid the Gihub
> ref (although it does seem silly to pretend that Github does not
> exist).

I completely agree with Adam and Nick's take on this issue.  Breaking
HTML export by removing htmlize is going to have a huge negative impact
on Org users and since the package is already free software what is the
point?

Regards,
Bernt



[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-18 Thread Eli Zaretskii
> From: Nicolas Goaziou 
> Cc: r...@gnu.org,  kaushal.m...@gmail.com,  n...@flqt.fr,  
> 32...@debbugs.gnu.org
> Date: Tue, 18 Sep 2018 11:37:15 +0200
> 
> This is a genuine question: what /exactly/ do you want Org developers to
> solve, assuming they can? Also, if they cannot, who is willing to give
> them a hand?

>From my POV, the immediate problem is to switch Org-publish from using
htmlize to htmlfontify.  Can this be done, please?





[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-18 Thread Nicolas Goaziou
Hello,

Eli Zaretskii  writes:

> This is an Org issue, so I would like to hear from Org developers
> before I make up my mind.

I read the thread multiple times already but I do not understand exactly
the issue risen.

>From the OP: "Emacs quotes Github, a non-free platform." If that's the
real problem, we can remove the location of the "htmlize" library from
the error message and be done with it. Note that the Org manual still
talks about iOS and Android, which are not free either.

>From Richard Stallman: "Emacs should not advise people to load anything
from outside Emacs". Org Export already advises people to load LaTeX
libraries, MathJax, optionally minted, etc. Org Babel requires external
libraries like "asy-mode.el" (ob-asymptote.el), "simple-httpd"
(ob-js.el)... This is a non-issue for us, because it is inherent to Org
and thus cannot be solved by Org.

>From Glenn Morris: "Emacs already includes htmlfontify, since 23.2. Is
there some obstacle to Org using that?" This is begging for a specific
solution to a not-so-well defined problem. In any case, Kaushal Modi
answered this one. It is nice if this happens, but could we first define
correctly the problem so we can tell if this is the only possible
solution for it?

>From Richard Stallman: "To motivate people to do this, I say we should
not ship another release with that reference to GitHub." The issue
pointed out here seems to be that Org developers or enthusiasts are not
motivated enough to make Org use htmlfontify instead of htmlize. Note
this is very different from the initial report. Richard Stallman then
suggests a possible fix for that issue. It may or may not work; after
all these years spent in education, "motivating people" is a topic that
mostly eludes me. Anyway, since this point contains both the question
and the answer, I don't know what Org could do about it.

This is a genuine question: what /exactly/ do you want Org developers to
solve, assuming they can? Also, if they cannot, who is willing to give
them a hand?

Regards,

-- 
Nicolas Goaziou0x80A93738





Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-17 Thread Nick Dokos
Adam Porter  writes:

> I'm not an expert on this package nor this situation, however, looking
> at the htmlize.el file shows:
>
> ;; Copyright (C) 1997-2003,2005,2006,2009,2011,2012,2014,2017,2018
>
> So it would appear that the package has existed longer than either
> GitHub or Org.  I'm guessing that its author moved its primary repo to
> GitHub after Org started using it.
>
> In hindsight, perhaps it would have been better to move htmlize into
> Emacs before adding it to Org proper.  But many things are clearer in
> hindsight.
>
> Regardless of where it is hosted, htmlize.el is Free Software, and it's
> an optional addon to Org.  We can encourage its author to add it to
> Emacs proper, or to ELPA.  But surely it's not necessary to censor the
> mention of "GitHub" in the manual; it's simply a fact that GitHub exists
> and that htmlize.el is currently hosted there.  It would seem
> unreasonable for the Org maintainers to have reacted to htmlize.el's
> moving to GitHub by removing htmlize.el support while it remains Free
> Software, yet that's the logical conclusion of this argument.
>

I had exactly the same reaction.

> So please do not remove support for this package because of where its
> repo happens to be hosted at the moment.  That would be a major
> regression, and it would not be in users' best interests.  It would not
> be fair to remove a major feature used by thousands of users and demand
> that "someone" (since there is no one ultimately responsible) rewrite
> large parts of ox-html.el to fix it.  It would at least seem fair for
> those insisting on the change to do the necessary work.
>

I don't usually +1 replies but I wanted to chime in my agreement with
Adam here.  Thanks for taking the time to put your (and my!) thoughts
into words.

If Github is indeed the sticking point, why can't it (the htmlize
repo) be cloned on the same server as org-mode (possibly as its own
repo, possibly as a git submodule)? It's not a fast moving target: a
handful or two of commits per year. The doc can then avoid the Gihub
ref (although it does seem silly to pretend that Github does not
exist).

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler




Re: [O] Bug: org-agenda-filter-by-top-heading does not filter [9.1.14 (release_9.1.14-908-gf1269e)]

2018-09-16 Thread Kyle Meyer
Hello,

Lem Ming  writes:

> In the agenda list `org-agenda-list` buffer, when I do
> `org-agenda-filter-by-top-headline` when the point is over a line with a
> headline, nothing is filtered.
>

I've never used org-agenda-filter-by-top-headline, but taking a quick
look at it and its helper, org-find-top-headline, the intention seems to
be to find the level-one parent of the current heading.  So, in your
example,

> * Root
> ** TODO task 2
> :tag_2:
>DEADLINE: <2018-09-14 Fri 12:00:00>
>:PROPERTIES:
>:ADD_TIME: <2018-09-07 Fri 23:47:00>
>:END:
> *** TODO task 2.1
> DEADLINE: <2018-09-14 Fri 11:00:00>
> :PROPERTIES:
> :ADD_TIME: <2018-09-07 Fri 23:47:00>
> :END:
[...]
> ** TODO task 7
>DEADLINE: <2018-09-14 Fri 12:00:00> SCHEDULED: <2018-09-12 Wed 10:00:00>

... it'd find "Root" if point were on any of the tasks.  If I'm reading
your report correctly, you're assuming that with point on the "task 2",
it'd take *that* as the top-level heading and filter to all the tasks
under it (task 2.1, etc).  Instead, it finds "Root" and filters to
everything thing under that, which---in your example file---is the same
thing, so you don't see any change.

-- 
Kyle



Re: [O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-16 Thread Adam Porter
I'm not an expert on this package nor this situation, however, looking
at the htmlize.el file shows:

;; Copyright (C) 1997-2003,2005,2006,2009,2011,2012,2014,2017,2018

So it would appear that the package has existed longer than either
GitHub or Org.  I'm guessing that its author moved its primary repo to
GitHub after Org started using it.

In hindsight, perhaps it would have been better to move htmlize into
Emacs before adding it to Org proper.  But many things are clearer in
hindsight.

Regardless of where it is hosted, htmlize.el is Free Software, and it's
an optional addon to Org.  We can encourage its author to add it to
Emacs proper, or to ELPA.  But surely it's not necessary to censor the
mention of "GitHub" in the manual; it's simply a fact that GitHub exists
and that htmlize.el is currently hosted there.  It would seem
unreasonable for the Org maintainers to have reacted to htmlize.el's
moving to GitHub by removing htmlize.el support while it remains Free
Software, yet that's the logical conclusion of this argument.

So please do not remove support for this package because of where its
repo happens to be hosted at the moment.  That would be a major
regression, and it would not be in users' best interests.  It would not
be fair to remove a major feature used by thousands of users and demand
that "someone" (since there is no one ultimately responsible) rewrite
large parts of ox-html.el to fix it.  It would at least seem fair for
those insisting on the change to do the necessary work.







[O] Bug: ODT export fails if NAME: and ref: equation [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/kdm/.emacs.d/elpa/org-20180910/)]

2018-09-14 Thread Ken Mankoff


Sorry if this is a triplicate bug report. I emailed this as a message (not bug 
report) to the Org list a week ago, but have seen no reply. I tried an official 
bug report last night which I *think* did not work (mailing from within "emacs 
-Q" does not "just work"), so here I try again.

If I have the following simple Org file, latest Org, and a clean emacs session 
(emacs -Q), ODT export fails. 

# == BEGIN MWE 
#+NAME: eq:foo
\begin{equation}
42
\end{equation}
See [[eq:foo]].
# == END MWE 

It does not fail if I comment out either of the #+NAME or the "[[eq:foo]]" 
lines. Note, perhaps tangentially related, that the manual shows "#+LABEL: ", 
but I'm using "+#NAME: ", and I thought LABEL was deprecated for NAME

https://www.gnu.org/software/emacs/manual/html_node/org/Labels-and-captions-in-ODT-export.html#Labels-and-captions-in-ODT-export

  -k.





Emacs  : GNU Emacs 25.2.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.21)
 of 2017-09-22, modified by Debian
Package: Org mode version 9.1.14 (9.1.14-1-g4931fc-elpa @ 
/home/kdm/.emacs.d/elpa/org-20180910/)

current state:
==
(setq
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-activate
  org-babel-speed-command-activate)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-confirm-shell-link-function 'yes-or-no-p
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(#[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-show-block-all append
local]
   5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-babel-show-result-all
append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-bibtex-headline-format-function #[257 "\300.\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-link-parameters '(("id" :follow org-id-open)
   ("rmail" :follow org-rmail-open :store
org-rmail-store-link)
   ("mhe" :follow org-mhe-open :store org-mhe-store-link)
   ("irc" :follow org-irc-visit :store org-irc-store-link)
   ("info" :follow org-info-open :export org-info-export
:store org-info-store-link)
   ("gnus" :follow org-gnus-open :store
org-gnus-store-link)
   ("docview" :follow org-docview-open :export
org-docview-export :store org-docview-store-link)
   ("bibtex" :follow org-bibtex-open :store
org-bibtex-store-link)
   ("bbdb" :follow org-bbdb-open :export org-bbdb-export
:complete org-bbdb-complete-link :store
org-bbdb-store-link)
   ("w3m" :store org-w3m-store-link) ("file+sys")
   ("file+emacs") ("doi" :follow org--open-doi-link)
   ("elisp" :follow org--open-elisp-link)
   ("file" :complete org-file-complete-link)
   ("ftp" :follow
(lambda (path) (browse-url (concat "ftp:" path
   ("help" :follow org--open-help-link)
   ("http" :follow
(lambda (path) (browse-url (concat "http:" path
   ("https" :follow
(lambda (path) (browse-url (concat "https:" path
   ("mailto" :follow
(lambda (path) (browse-url (concat "mailto:; path
   ("news" :follow
(lambda (path) (browse-url (concat "news:; path
   ("shell" :follow org--open-shell-link))
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 )





[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-14 Thread Eli Zaretskii
> From: Richard Stallman 
> Date: Thu, 13 Sep 2018 22:55:15 -0400
> Cc: n...@flqt.fr, 32...@debbugs.gnu.org, m...@nicolasgoaziou.fr
> 
>   > >From what I remember, there is not objection to use that instead; it's
>   > just that someone has to work on converting ox-html to use htmlfontify
>   > instead of htmlize.
> 
> To motivate people to do this, I say we shouild not ship another
> release with that reference to GitHub.  Eli, do you agree?

This is an Org issue, so I would like to hear from Org developers
before I make up my mind.





Re: [O] Bug: org-agenda-filter-by-top-heading does not filter [9.1.14 (release_9.1.14-908-gf1269e)]

2018-09-13 Thread Lem Ming
I tried with org-mode version 9.0.10 and 9.0.1.
There is still no filtering when I do ^ in org agenda mode when the point
is anywhere on a line where there is a task.

I observe that:
- The version 9.0.1 dates to November 2016.
- org-agenda-filter-by-top-headline is a very useful function.

It probably means that if it was a bug it would probably have been fix by
then. But it is not. Which makes me think it is probably not a bug and that
I am probably not using this function the right way.

How do I filter the tasks listed in the agenda list by top headline?

Regards.


[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-13 Thread Richard Stallman
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > >From what I remember, there is not objection to use that instead; it's
  > just that someone has to work on converting ox-html to use htmlfontify
  > instead of htmlize.

To motivate people to do this, I say we shouild not ship another
release with that reference to GitHub.  Eli, do you agree?


-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







[O] bug#32722: bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-13 Thread Samuel Wales
(htmlize-buffer-substring-no-invisible b e)

is this function available in emacs?

if not, it would be good to extract it and put it in emacs, or write
one for emacs.


On 9/13/18, Kaushal Modi  wrote:
> On Thu, Sep 13, 2018 at 11:28 AM Glenn Morris  wrote:
>>
>> Emacs already includes htmlfontify, since 23.2.
>> Is there some obstacle to Org using that? (bug#7506)
>
> This has been discussed before on the Org mailing list.
>
> From what I remember, there is not objection to use that instead; it's
> just that someone has to work on converting ox-html to use htmlfontify
> instead of htmlize.
>
>


-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.





Re: [O] bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-13 Thread Kaushal Modi
On Thu, Sep 13, 2018 at 11:28 AM Glenn Morris  wrote:
>
> Emacs already includes htmlfontify, since 23.2.
> Is there some obstacle to Org using that? (bug#7506)

This has been discussed before on the Org mailing list.

>From what I remember, there is not objection to use that instead; it's
just that someone has to work on converting ox-html to use htmlfontify
instead of htmlize.



[O] bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-13 Thread Glenn Morris
Richard Stallman wrote:

> If htmlize is useful, we should put it into Emacs.
> Is there some obstacle to that?

Emacs already includes htmlfontify, since 23.2.
Is there some obstacle to Org using that? (bug#7506)





[O] bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-13 Thread Nicolas Floquet
Le mercredi 12 septembre 2018 à 18:48 +0300, Eli Zaretskii a écrit :
> Could you please report this to the Org developers? Thanks.

It's done. Thanks.

Le mercredi 12 septembre 2018 à 23:35 -0400, Richard Stallman a écrit :
> Emacs should not advise people to load anything from outside Emacs
> (counting ELPA).  So this needs to be deleted.
> 
> If htmlize is useful, we should put it into Emacs.
> Is there some obstacle to that?

Thank you rms.


-- 
| Numérion  |  Nicolas Floquet |
+--+
| Services informatiques en logiciels libres   |
| XMPP : nf...@jabber.fr | Tél : 06.32.93.03.51|
| Ğ1 : BjZFP7UpKjJ9hbavhT2Ep2hP58noXp6xdPY4awsX17yD|
| PGP : 94C7 641B 719E B06A F406  7AB3 3709 C700 E548 F996 | 
+--+






Re: [O] Bug: Nested \caption and \label in LaTeX export [9.1.14 (9.1.14-1-g4931fc-elpaplus @ /home/simon/.emacs.d/elpa/26.1/develop/org-plus-contrib-20180910/)]

2018-09-13 Thread Simon Braß
Dear Eric,

thanks for the fast reply!
Indeed, I had a look at the lshort documentation.
It actually never states that \label must come after the full \caption{}
command - nesting works - good to know.
I'm sorry for the inconvenience.

Cheers,
Simon

On 9/13/18 8:05 AM, Eric S Fraga wrote:
> On Tuesday, 11 Sep 2018 at 09:31, Simon Braß wrote:
>> Exporting a table (or figure) with a CAPTION and NAME tag leads to
>> following result:
>> \caption{\label{whatever-tag} I am a caption.}
>> Any LaTeX compiler won't understand this line correctly and won't be able
>> to reference to the assigned label.
> Simon,
>
> In my experience, LaTeX has no problem with this.  I have always (when
> writing LaTeX directly) put the label inside the caption as it's the
> caption that defines the numbering of the table/figure.  Have you
> actually tried this?  What happens when you do?
>



Re: [O] Bug: Nested \caption and \label in LaTeX export [9.1.14 (9.1.14-1-g4931fc-elpaplus @ /home/simon/.emacs.d/elpa/26.1/develop/org-plus-contrib-20180910/)]

2018-09-13 Thread Eric S Fraga
On Tuesday, 11 Sep 2018 at 09:31, Simon Braß wrote:
> Exporting a table (or figure) with a CAPTION and NAME tag leads to
> following result:
> \caption{\label{whatever-tag} I am a caption.}
> Any LaTeX compiler won't understand this line correctly and won't be able
> to reference to the assigned label.

Simon,

In my experience, LaTeX has no problem with this.  I have always (when
writing LaTeX directly) put the label inside the caption as it's the
caption that defines the numbering of the table/figure.  Have you
actually tried this?  What happens when you do?

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-753-g2ec5d3



[O] bug#32722: 26.1; Org-publish depend on non-free platform ?

2018-09-12 Thread Richard Stallman
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

Emacs should not advise people to load anything from outside Emacs
(counting ELPA).  So this needs to be deleted.

If htmlize is useful, we should put it into Emacs.
Is there some obstacle to that?

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







[O] Bug: org-agenda-filter-by-top-heading does not filter [9.1.14 (release_9.1.14-908-gf1269e)]

2018-09-11 Thread Lem Ming
I am learning org-mode by trying the several features one by one.

In the agenda list `org-agenda-list` buffer, when I do
`org-agenda-filter-by-top-headline` when the point is over a line with a
headline, nothing is filtered.

I use the minimal setup as described with the most recent org version as
specified here:
https://orgmode.org/org.html#Feedback

Here is the content of the files in org-agenda-files:

f1.org
```
* Root
** TODO task 1
:tag_1:
   DEADLINE: <2018-09-14 Fri 12:00:00>
   :PROPERTIES:
   :ADD_TIME: <2018-09-07 Fri 23:47:00>
   :END:
*** TODO task 1.1
DEADLINE: <2018-09-14 Fri 11:00:00>
:PROPERTIES:
:ADD_TIME: <2018-09-07 Fri 23:47:00>
:END:
*** DONE task 1.2
CLOSED: [2018-09-09 Sun 23:53:00] DEADLINE: <2018-09-14 Fri 11:00:00>
:PROPERTIES:
:ADD_TIME: <2018-09-07 Fri 23:47:00>
:END:
```

f2.org
```
* Root
** TODO task 2
:tag_2:
   DEADLINE: <2018-09-14 Fri 12:00:00>
   :PROPERTIES:
   :ADD_TIME: <2018-09-07 Fri 23:47:00>
   :END:
*** TODO task 2.1
DEADLINE: <2018-09-14 Fri 11:00:00>
:PROPERTIES:
:ADD_TIME: <2018-09-07 Fri 23:47:00>
:END:
*** DONE task 2.2
CLOSED: [2018-09-09 Sun 23:53:00] DEADLINE: <2018-09-14 Fri 11:00:00>
:PROPERTIES:
:ADD_TIME: <2018-09-07 Fri 23:47:00>
:END:
** DONE task 3 [100%]
:tag_3:
   CLOSED: [2018-09-10 Mon 23:57:22] DEADLINE: <2018-09-14 Fri 12:00:00>
   :PROPERTIES:
   :ADD_TIME: <2018-09-06 Thu 23:47:00>
   :END:
*** DONE task 3.1
CLOSED: [2018-09-10 Mon 23:57:20] DEADLINE: <2018-09-14 Fri 11:00:00>
:PROPERTIES:
:ADD_TIME: <2018-09-06 Thu 23:47:00>
:END:
*** DONE task 3.2
CLOSED: [2018-09-09 Sun 23:53:00] DEADLINE: <2018-09-14 Fri 11:00:00>
:PROPERTIES:
:ADD_TIME: <2018-09-06 Thu 23:47:00>
:END:
** TODO task 4
   DEADLINE: <2018-09-13 Thu 12:00:00> SCHEDULED: <2018-09-14 Fri 23:55:00>
** TODO task 5
   DEADLINE: <2018-09-11 Tue 12:00:00> SCHEDULED: <2018-09-06 Thu 10:00:00>
** TODO task 6
   DEADLINE: <2018-09-13 Thu 12:00:00> SCHEDULED: <2018-09-09 Sun 10:00:00>
** TODO task 7
   DEADLINE: <2018-09-14 Fri 12:00:00> SCHEDULED: <2018-09-12 Wed 10:00:00>
```

Am I not using `org-agenda-filter-by-top-headline` correctly?
What should I do to filter the agenda list by top headline?

Regards.

===

Emacs  : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
 of 2018-07-05
Package: Org mode version 9.1.14 (release_9.1.14-908-gf1269e)

current state:
==
(setq
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-agenda-files '("~/tmp/orgmode/agenda/f2.org" "~/tmp/orgmode/agenda/
f1.org")
 org-mode-hook '((closure
  (org--rds reftex-docstruct-symbol orgtbl-line-start-regexp
   org-element-greater-elements org-table-coordinate-overlays
   org-table-auto-blank-field org-clock-history
org-agenda-current-date
   org-with-time org-defdecode org-def org-read-date-inactive
org-ans2
   org-ans1 org-columns-current-fmt-compiled org-clock-current-task
   org-clock-effort org-agenda-skip-function
   org-agenda-skip-comment-trees org-agenda-archives-mode
   org-end-time-was-given org-time-was-given org-log-note-extra
   org-log-note-purpose org-log-post-message
org-last-inserted-timestamp
   org-last-changed-timestamp org-entry-property-inherited-from
   org-blocked-by-checkboxes org-state
   org-agenda-headline-snapshot-before-repeat
   org-capture-last-stored-marker org-agenda-start-on-weekday
   org-agenda-buffer-tmp-name clean-buffer-list-kill-buffer-names
   org-id-link-to-org-use-id org-agenda-buffer-name
org-priority-regexp
   org-mode-abbrev-table org-mode-syntax-table buffer-face-mode-face
   org-mode-map org-tbl-menu org-org-menu org-struct-menu
org-entities
   org-last-state org-id-track-globally org-clock-start-time
texmathp-why
   remember-data-file org-agenda-tags-todo-honor-ignore-options
   iswitchb-temp-buflist calc-embedded-open-mode
   calc-embedded-open-formula calc-embedded-close-formula
   align-mode-rules-list org-emphasis-alist
   org-emphasis-regexp-components org-export-registered-backends
   org-modules org-babel-load-languages
org-indent-indentation-per-level
   org-element-paragraph-separate ffap-url-regexp
   org-inlinetask-min-level t)
  nil
  (add-hook (quote change-major-mode-hook) (quote org-show-all)
   (quote append) (quote local))
  )
 (closure
  (org-bracket-link-regexp org-src-window-setup *this*
   org-babel-confirm-evaluate-answer-no org-src-preserve-indentation
   org-src-lang-modes 

Re: [O] Bug: org-string-display throws on image display property [9.1.9 (release_9.1.9-65-g5e4542 @ /home/blc/.local/share/emacs/27.0.50/lisp/org/)]

2018-09-03 Thread Basil L. Contovounesios
Nicolas Goaziou  writes:

> "Basil L. Contovounesios"  writes:
>
>> Severity: minor
>>
>> 0. emacs -Q
>> 1. M-x toggle-debug-on-error RET
>> 2. Evaluate the following:
>>
>>   (require 'org)
>>   (org-string-display
>>(propertize " " 'display '(image :type svg
>> :file "/path/to/image.svg")))
>>
>> This gives the following error backtrace:
>>
>> Debugger entered--Lisp error: (wrong-type-argument sequencep t)
>
> `org-string-display' doesn't exist anymore in master (Org 9.2). However,
> there is the same error with `org-string-width'. 
>
> What is `org-string-width' supposed to do on your example? Probably
> return an error.

I realise that the 'display' property is a pretty complicated beast, so
it may be impractical for 'org-string-width' to do this, but I think
more accurate/useful behaviour would be to calculate the displayed width
of the image via 'image-size' or 'image-display-size', rather than
signalling an error.

>> I realise that org-string-display is a relatively obscure function that
>> was probably not designed with image or other complex display properties
>> in mind, but AFAICT the following is a pretty obvious "fix", given that
>> the surrounding code expects 'value' to be a string or nil, but never t:
>>
>> diff --git a/lisp/org/org-macs.el b/lisp/org/org-macs.el
>> index 583633605f..5ab069e6a2 100644
>> --- a/lisp/org/org-macs.el
>> +++ b/lisp/org/org-macs.el
>> @@ -108,7 +108,7 @@ org-string-display
>> ;; string (face...).
>> (let* ((display (plist-get props 'display))
>>(value (if (stringp display) display
>> -   (cl-some #'stringp display
>> +   (cl-find-if #'stringp display
>>   (when value
>> (apply #'propertize
>>;; Displayed string could contain
>>
>>
>> With this change, the return value of org-string-display does not really
>> make sense for images, but at least the function doesn't barf on complex
>> but valid display properties.  WDYT?
>
> If `org-string-width' returns nil, it will ensue an error somewhere
> further in the code. So returning an error right here is better (or
> find a way to compute the width of an image in columns).

Why/when would 'org-string-width' return nil?  My suggestion was to
replace 'cl-some' with 'cl-find-if', because the value of
(cl-some #'stringp ...) is a boolean, not a sequence.

To clarify - I am not suggesting that 'org-string-width' should never
signal an error; I am only suggesting that the current
(wrong-type-argument sequencep t) error is due to inappropriate use of
'cl-some'.  My comments may already be outdated, though, since they
refer to the version of org-macs.el shipping with latest Emacs master.

> As another data point, `string-width' returns 1 on your example, which
> is probably wrong.

Neither 'string-width' nor 'current-column' take 'display' properties
into account; see e.g. https://emacs.stackexchange.com/q/44495/15748.
But that's an Emacs feature request of its own.

Thanks,

-- 
Basil



Re: [O] Bug: org-string-display throws on image display property [9.1.9 (release_9.1.9-65-g5e4542 @ /home/blc/.local/share/emacs/27.0.50/lisp/org/)]

2018-09-03 Thread Nicolas Goaziou
Hello,

"Basil L. Contovounesios"  writes:

> Severity: minor
>
> 0. emacs -Q
> 1. M-x toggle-debug-on-error RET
> 2. Evaluate the following:
>
>   (require 'org)
>   (org-string-display
>(propertize " " 'display '(image :type svg
> :file "/path/to/image.svg")))
>
> This gives the following error backtrace:
>
> Debugger entered--Lisp error: (wrong-type-argument sequencep t)

`org-string-display' doesn't exist anymore in master (Org 9.2). However,
there is the same error with `org-string-width'. 

What is `org-string-width' supposed to do on your example? Probably
return an error.

> I realise that org-string-display is a relatively obscure function that
> was probably not designed with image or other complex display properties
> in mind, but AFAICT the following is a pretty obvious "fix", given that
> the surrounding code expects 'value' to be a string or nil, but never t:
>
> diff --git a/lisp/org/org-macs.el b/lisp/org/org-macs.el
> index 583633605f..5ab069e6a2 100644
> --- a/lisp/org/org-macs.el
> +++ b/lisp/org/org-macs.el
> @@ -108,7 +108,7 @@ org-string-display
>  ;; string (face...).
>  (let* ((display (plist-get props 'display))
> (value (if (stringp display) display
> -(cl-some #'stringp display
> +   (cl-find-if #'stringp display
>(when value
>  (apply #'propertize
> ;; Displayed string could contain
>
>
> With this change, the return value of org-string-display does not really
> make sense for images, but at least the function doesn't barf on complex
> but valid display properties.  WDYT?

If `org-string-width' returns nil, it will ensue an error somewhere
further in the code. So returning an error right here is better (or
find a way to compute the width of an image in columns).

As another data point, `string-width' returns 1 on your example, which
is probably wrong.

WDYT?

Regards,

-- 
Nicolas Goaziou



[O] Bug: org-string-display throws on image display property [9.1.9 (release_9.1.9-65-g5e4542 @ /home/blc/.local/share/emacs/27.0.50/lisp/org/)]

2018-09-03 Thread Basil L. Contovounesios
Severity: minor

0. emacs -Q
1. M-x toggle-debug-on-error RET
2. Evaluate the following:

  (require 'org)
  (org-string-display
   (propertize " " 'display '(image :type svg
:file "/path/to/image.svg")))

This gives the following error backtrace:

Debugger entered--Lisp error: (wrong-type-argument sequencep t)
  #f(compiled-function (s property filter) #)(t invisible 
#f(compiled-function (props) #))
  #f(compiled-function (s) #)(t)
  #f(compiled-function (props) #)((display (image :type svg 
:file "/path/to/image.svg")))
  #f(compiled-function (s property filter) #)(#(" " 0 1 
(display (image :type svg :file "/path/to/image.svg"))) display 
#f(compiled-function (props) #))
  #f(compiled-function (build-from-parts prune-invisible s) #)(#f(compiled-function (s property filter) #) 
#f(compiled-function (s) #) #(" " 0 1 (display (image :type 
svg :file "/path/to/image.svg"
  org-string-display(#(" " 0 1 (display (image :type svg :file 
"/path/to/image.svg"
  eval((org-string-display (propertize " " 'display '(image :type svg :file 
"/path/to/image.svg"))) nil)
  elisp--eval-last-sexp(t)
  eval-last-sexp(t)
  eval-print-last-sexp(nil)
  funcall-interactively(eval-print-last-sexp nil)
  call-interactively(eval-print-last-sexp nil nil)
  command-execute(eval-print-last-sexp)

I realise that org-string-display is a relatively obscure function that
was probably not designed with image or other complex display properties
in mind, but AFAICT the following is a pretty obvious "fix", given that
the surrounding code expects 'value' to be a string or nil, but never t:

diff --git a/lisp/org/org-macs.el b/lisp/org/org-macs.el
index 583633605f..5ab069e6a2 100644
--- a/lisp/org/org-macs.el
+++ b/lisp/org/org-macs.el
@@ -108,7 +108,7 @@ org-string-display
 		   ;; string (face...).
 		   (let* ((display (plist-get props 'display))
 			  (value (if (stringp display) display
-   (cl-some #'stringp display
+   (cl-find-if #'stringp display
 			 (when value
 			   (apply #'propertize
   ;; Displayed string could contain

With this change, the return value of org-string-display does not really
make sense for images, but at least the function doesn't barf on complex
but valid display properties.  WDYT?

Thanks,

-- 
Basil

Emacs  : GNU Emacs 27.0.50 (build 3, x86_64-pc-linux-gnu, X toolkit, Xaw3d 
scroll bars)
 of 2018-09-01
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ 
/home/blc/.local/share/emacs/27.0.50/lisp/org/)


Re: [O] Bug: Org Table Performance Issue/Regression

2018-09-03 Thread Nicolas Goaziou
Hello,

Tim Baumgard  writes:

>> On Jun 26, 2018, at 4:58 AM, Nicolas Goaziou wrote:
>> 
>> Could you send the result of your profiling (using both Elp and
>> profiler would be nice) on an uncompiled Org?
>
> I've attached ten profiler results: Two are from 25.3 with the garbage 
> collector
> running normally, two are from 25.3 with the garbage collector "disabled" as
> described in my previous email, two are from 26.1 with the garbage collector
> running normally, two are from 26.1 with the garbage collector "disabled," and
> two are the Elp profiles--I used elp-instrument-package--for both versions.
>
> In case it helps, my process to obtain these has been:
>
> 1. I use the test.org file from my previous email with the test row duplicated
>so that it occurs 3500 times. I can't remember how many rows I used in my
>previous tests.
> 2. I invoke Emacs by calling "Emacs.app/Contents/MacOS/Emacs -Q"
> 3. I use "M-x load-file" to load the test init.el file I included in my 
> previous
>email, with the last two lines commented out or not depending on what I'm
>testing.
> 4. I then open the test.org file and go to column A in the last row.
> 5. I then start one of the profilers, hit enter, hit shift+enter
>(org-table-copy-down), and then get the report from the profiler.
>
> Let me know if I can provide anything else.

I think master branch behaves better now. Could you confirm it?

Regards,

-- 
Nicolas Goaziou0x80A93738



[O] Bug: Capturing an entry without final endline modifies heading structure [9.1.14 (9.1.14-dist @ /usr/share/emacs/25.2/site-lisp/elpa/org-9.1.11/)]

2018-09-02 Thread Christoph Groth
Hello,

I'm using org's capture functionality to file new entries for my agenda.
I noticed a problem when capturing entries to be placed in the middle of
a file (for example, I have a subtree for "notes" that comes before
"miscellaneous"): when the captured text ends without a trailing endline
character, it will be inserted as such into the org file and thus modify
the overall heading structure.  For example, inserting a note may lead
to the following situation:

** Note without trailing endline
[2018-09-02 Sun 13:10]
example text* miscellaneous

IMHO this qualifies as a bug, because it's easy to accidentally corrupt
the heading structure of a file.

Cheers,
Christoph

Emacs  : GNU Emacs 25.2.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
 of 2018-07-11, modified by Debian
Package: Org mode version 9.1.14 (9.1.14-dist @ 
/usr/share/emacs/25.2/site-lisp/elpa/org-9.1.11/)

current state (relevant excerpt):

(setq
 org-capture-templates '(("u" "unscheduled" entry
  (file+headline "" "miscellaneous") "* TODO %?\n%U")
 ("U" "" entry (file+headline "" "miscellaneous")
  "* TODO %?\n%a\n%U")
 ("s" "scheduled" entry
  (file+headline "" "miscellaneous")
  "* TODO %?\nSCHEDULED: %^t\n%U")
 ("S" "" entry (file+headline "" "miscellaneous")
  "* TODO %?\nSCHEDULED: %^t\n%a\n%U")
 ("m" "maybe" entry (file+headline "" "miscellaneous")
  "* MAYBE %?\n%U")
 ("M" "" entry (file+headline "" "miscellaneous")
  "* MAYBE %?\n%a\n%U")
 ("d" "deadline" entry
  (file+headline "" "miscellaneous")
  "* TODO %?\nDEADLINE: %^t\n%U")
 ("D" "" entry (file+headline "" "miscellaneous")
  "* TODO %?\nDEADLINE: %^t\n%a\n%U")
 ("a" "appointment" entry
  (file+headline "" "miscellaneous") "* %?\n%^t\n%U")
 ("A" "" entry (file+headline "" "miscellaneous")
  "* %?\n%^t\n%a\n%U")
 ("r" "reply" entry (file+headline "" "miscellaneous")
  "* TODO Reply to %:fromname%?\nSCHEDULED: 
%^t\n%a\n%U")
 ("n" "note" entry (file+headline "" "notes")
  "* %?\n%U")
 ("i" "interruption" entry
  (file+headline "" "interruptions") "* %? :work:\n%U"
  :clock-in t :clock-resume t)
 )
 )



Re: [O] Bug: org-indent-boundary-char doesn't have org-indent face [9.1.9 (release_9.1.9-65-g5e4542 @ c:/Program Files/emacs-26.1-x86_64/share/emacs/26.1/lisp/org/)]

2018-08-21 Thread Nicolas Goaziou
Hello,

HIRATA Tadashi  writes:

> I found a bug that org-indent-boundary-char doens't have
> org-indent face property in org-indent-mode. This causes an
> appearance issue when you use org-mode with whitespace-mode
> that you can't control org-indent-boundary-char's face
> neither whitespace-space face nor org-indent face.
>
> Here is a quick patch to fix the problem. (though I test it
> in 9.1.9, but it should work well in the latest version).

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] [Bug] org-attach-set-directory

2018-08-21 Thread Nicolas Goaziou
Hello,

Florian Lindner  writes:

> doing C-a s  on an entry with an existing attachement produces
>
> make-directory: Die Datei existiert bereits: /home/florian/test/data/
>
> (translation: File already exists)
>
> Actually, I implemented this functionality with the help of Nicolas Goaziou, 
> but it seems an org mode or emacs upgrade broke it.
>
> I will try to debug that further, but right now, my time is very limited, 
> only undershot by my elisp knowledge.
>
> Maybe someone can more quickly fix that... ;-)
>
> Best,
> Florian
>
> Backtrace:
>
> Debugger entered--Lisp error: (file-already-exists "Die Datei existiert 
> bereits" "/home/florian/test/mydata")
>   make-directory-internal("/home/florian/test/mydata")
>   make-directory("/home/florian/test/mydata" nil)
>   
> copy-directory("/home/florian/test/data/c1/32d552-b7bb-43b1-b0d8-c57c00d61f9b"
> "/home/florian/test/mydata" t nil t)


It looks like "/home/florian/test/mydata" is not a valid directory name.
It should end with a forward slash.


Regards,

-- 
Nicolas Goaziou



[O] Bug - #+begin_comment, etc surrounding minipage

2018-08-20 Thread Charles Millar

Hi,

When exporting to pdf via LaTeX, the region between the #+begin_comment 
and the #+end_comment does not comment out:


*** sub,sub-heading one
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage

#+begin_comment

*** sub,sub-heading two
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage

*** sub,sub-heading three
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage*** sub,sub-heading one
#+attr_latex: :options  [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options  [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage

#+end_comment

Instead the #+begin_comment and #+end_comment lines are printed out 
(sort of weirdly) and everything in between as well.


If I surround the region with a \begin{comment} and \end{comment} - all 
is well.


Org mode version 9.1.13 (release_9.1.13-901-g638f32 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 48, x86_64-pc-linux-gnu, GTK+ Version 3.22.29) 
of 2018-06-29


Charlie Millar



Re: [O] Bug: truncate lines when setupfile [9.0.5 (9.0.5-elpa @ /home/xavier/.emacs.d/elpa/org-20170210/)]

2018-08-20 Thread Nicolas Goaziou
Hello,

Xavier Leleu  writes:

> The default truncate-line option turns off when the org-file contains
> a #+SETUPFILE: mysetupfile.setup. M-x toggle-truncate-lines gets
> truncation back. 

I cannot reproduce it. Could you provide an ECM?

Thank you.

Regards,

-- 
Nicolas Goaziou



[O] Bug: git clone https://code.orgmode.org/bzg/org-mode.git fails with fatal: unable to access 'https://code.orgmode.org/bzg/org-mode.git/': server certificate verification failed. CAfile: /etc/ssl/c

2018-08-19 Thread Brent Goodrick


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.

This is not a bug with org-mode but seems to be a configuration
problem with the website and/or the underlying git server there:

As of Sun Aug 19 08:27:11 PDT 2018 the clone operation on my Ubuntu
18.04 laptop fails with:

nunyabidness@oryx:/tmp/org-mode.direct$ git clone 
https://code.orgmode.org/bzg/org-mode.git
Cloning into 'org-mode'...
fatal: unable to access 'https://code.orgmode.org/bzg/org-mode.git/': server 
certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt 
CRLfile: none
nunyabidness@oryx:/tmp/org-mode.direct$

I've updated my hosts CA's via the instructions found at
https://stackoverflow.com/a/35824116/257924 to no avail.

I checked my system time is constantly up to date, so it is not a NTP
issue.

I noted that even browsing to the website at https://orgmode.org
required me to add a certificate exception to my browser.

I originally did a git pull in order to get my local installed copy of
org-mode up to date, and got the same error, so I'm reporting the 'git
clone' command above into a /tmp directory just to be sure it is not
due to something I've fouled up in my normal directory.


Emacs  : GNU Emacs 25.2.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.21)
 of 2017-09-22, modified by Debian
Package: Org mode version 9.1.7 (release_9.1.7-523-g594b2d @ 
/home/nunyabidness/emacs_lisp_imported/org-mode/org-mode/lisp/)

current state:
==
(setq
 org-id-locations-file "/home/nunyabidness/that_org_dir/.org-id-locations"
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 outline-minor-mode-hook '(wikipedia-outline-magic-keys (lambda nil (require 
(quote outline-magic
 org-clock-persist-file "/home/nunyabidness/that_org_dir/org-clock-save.el"
 org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
 org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function
 org-confirm-shell-link-function 'yes-or-no-p
 org-id-link-to-org-use-id t
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-clock-idle-time 10
 org-startup-folded nil
 org-file-apps '((auto-mode . emacs) ("\\.mm\\'" . default)
 ("\\.x?html?\\'" lambda (file link) (browse-url-of-file 
(expand-file-name file))) ("\\.pdf\\'" . default))
 org-tab-before-tab-emulation-hook '(org-tempo-complete-tag)
 org-export-with-sub-superscripts nil
 org-return-follows-link t
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-default-notes-file "/home/nunyabidness/that_org_dir/notes.org"
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
 org-odt-format-headline-function 'org-odt-format-headline-default-function
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-html-head-include-default-style nil
 org-mode-hook '(org-tempo-setup org-clock-load bg-org-mode-hook
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-show-all append local] 5]
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-babel-show-result-all append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-refile-targets '((nil :maxlevel . 9) (org-agenda-files :maxlevel . 9))
 org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-ascii-format-drawer-function #[771 "\207" [] 4 "\n\n(fn NAME CONTENTS 
WIDTH)"]
 org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
 org-clock-persist t
 org-refile-use-outline-path 'file
 org-directory "/home/nunyabidness/that_org_dir"
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-plantuml-jar-path "/home/nunyabidness/plantuml/plantuml.jar"
 org-edit-src-auto-save-idle-delay 5
 org-todo-keywords '((sequence "TODO(t)" "|" "DONE(d)" "SHELVED(s)" 
"DELEGATED(e)"))
 org-babel-tangle-lang-exts '(("python" . "py") ("emacs-lisp" . "el") ("elisp" 
. "el"))
 org-confirm-elisp-link-function 'bg-org-confirm-elisp-link
 org-html-htmlize-output-type 'css
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 outline-mode-hook '((lambda nil (require 

Re: [O] Bug: Broken link in documentation

2018-08-19 Thread Nicolas Goaziou
Hello,

Julien Palard  writes:

> I'm new to Org mode and spotted a broken link at the bottom of 
> https://orgmode.org/features.html : mobileorg.ncogni.to
>
> $ curl -s https://orgmode.org/features.html | grep 
> http://mobileorg.ncogni.to/
> Richard Moreland has developed  href="http://mobileorg.ncogni.to/;>MobileOrg, a free software for iPhone 
> and
> $ curl -i mobileorg.ncogni.to
> curl: (6) Could not resolve host: mobileorg.ncogni.to

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: Archiving items with org-attach-archive-delete set to 'query' always asks for confirmation

2018-08-15 Thread Kyle Meyer
Luciano Passuello  writes:

> Hello Kyle,
>
> That worked perfectly for all my basic test cases.

Great, pushed to master as ab1f7712d.

-- 
Kyle



Re: [O] Bug: Archiving items with org-attach-archive-delete set to 'query' always asks for confirmation

2018-08-11 Thread Luciano Passuello
Hello Kyle,

That worked perfectly for all my basic test cases.
Thanks!
On Fri, Aug 10, 2018 at 10:44 PM Kyle Meyer  wrote:
>
> Luciano Passuello  writes:
>
> > When I set org-attach-archive-delete to query, Org is supposed to ask
> > me for confirmation when archiving entries with attachments. However,
> > I am always asked for confirmation,  regardless if the item has
> > attachments in the first place. This is to me clearly undesirable
> > behavior.
>
> I agree, that doesn't sound desirable (though I've never used this
> feature, so perhaps I'm missing something).
>
> > Looking at the source code for org-attach, at line 573, that's indeed
> > what code tells us.
> > https://code.orgmode.org/bzg/org-mode/src/master/lisp/org-attach.el
> >
> > My uninformed suggestion is to call org-attach-delete-all without the
> > force parameter, using the confirmation code already in
> > org-attach-delete-all.
>
> That would cover the org-attach-archive-delete=query case, but it'd also
> ask for confirmation in the org-attach-archive-delete=t case.
>
> How about this?
>
> -- >8 --
> Subject: [PATCH] org-attach: Don't query unnecessarily about archiving
>
> * lisp/org-attach.el (org-attach-archive-delete-maybe): Don't query
> about deleting attachments if the entry doesn't have any attachments.
> ---
>  lisp/org-attach.el | 6 ++
>  1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/lisp/org-attach.el b/lisp/org-attach.el
> index 192815f4f..53389f782 100644
> --- a/lisp/org-attach.el
> +++ b/lisp/org-attach.el
> @@ -574,10 +574,8 @@ (defun org-attach-archive-delete-maybe ()
>"Maybe delete subtree attachments when archiving.
>  This function is called by `org-archive-hook'.  The option
>  `org-attach-archive-delete' controls its behavior."
> -  (when (if (eq org-attach-archive-delete 'query)
> -   (yes-or-no-p "Delete all attachments? ")
> - org-attach-archive-delete)
> -(org-attach-delete-all t)))
> +  (when org-attach-archive-delete
> +(org-attach-delete-all (not (eq org-attach-archive-delete 'query)
>
>
>  ;; Attach from dired.
> --
> 2.18.0
>



[O] [BUG] Duplicate characters in help string when filtering by tag

2018-08-10 Thread Matt Lundin
I'm finding that when I call org-agenda-filter-by-tag, the string of
character hints is long, with lots of duplicates. E.g.,

Filter by tag [hpcwhpcwhpcwhpcwhpcwhpcwhpcwhpcwhpcwhpcw ]:tag-char, [TAB]:tag, 
[/]:off, [+/-]:filter/exclude, [q]:quit [3 times]

A git bisect reveals that this bug began with commit
2056b60aae528d0ba663d8b3804dc69e98993f1c. After a bit of investigating,
I've found the cause: org--tag-add-to-alist no longer removes duplicate
tags if they belong in a tag group. 

Let me provide a minimal example to illustrate. Take the following
setting:

(setq org-tag-alist
  '((:startgroup)
("home" . ?h)
("phone" . ?p)
("computer" . ?c)
("work" . ?w)
(:endgroup)))

If one has 10 agenda files (none of which has a local #+TAGS
declaration), org-tag-alist-for-agenda will end up containing those tags
multiple times:

--8<---cut here---start->8---
org-tag-alist-for-agenda is a variable defined in ‘org.el’.
Its value is
(#1=(:startgroup)
#2=("home" . 104)
#3=("phone" . 112)
#4=("computer" . 99)
#5=("work" . 119)
#6=(:endgroup)
#1# #2# #3# #4# #5# #6# #1# #2# #3# #4# #5# #6# #1# #2# #3# #4# #5# #6# #1# 
#2# #3# #4# #5# #6# #1# #2# #3# #4# #5# #6# #1# #2# #3# #4# #5# #6# #1# #2# #3# 
#4# #5# #6# #1# #2# #3# #4# #5# #6# #1# #2# #3# #4# #5# #6#)
--8<---cut here---end--->8---

As a result, the help prompt for org-filter-tags-for-agenda looks like
this (notice the duplicate characters):

Filter by tag [hpcwhpcwhpcwhpcwhpcwhpcwhpcwhpcwhpcwhpcw ]:tag-char, [TAB]:tag, 
[/]:off, [+/-]:filter/exclude, [q]:quit [3 times]

Best,
Matt





Re: [O] Bug: Archiving items with org-attach-archive-delete set to 'query' always asks for confirmation

2018-08-10 Thread Kyle Meyer
Luciano Passuello  writes:

> When I set org-attach-archive-delete to query, Org is supposed to ask
> me for confirmation when archiving entries with attachments. However,
> I am always asked for confirmation,  regardless if the item has
> attachments in the first place. This is to me clearly undesirable
> behavior.

I agree, that doesn't sound desirable (though I've never used this
feature, so perhaps I'm missing something).

> Looking at the source code for org-attach, at line 573, that's indeed
> what code tells us.
> https://code.orgmode.org/bzg/org-mode/src/master/lisp/org-attach.el
>
> My uninformed suggestion is to call org-attach-delete-all without the
> force parameter, using the confirmation code already in
> org-attach-delete-all.

That would cover the org-attach-archive-delete=query case, but it'd also
ask for confirmation in the org-attach-archive-delete=t case.

How about this?

-- >8 --
Subject: [PATCH] org-attach: Don't query unnecessarily about archiving

* lisp/org-attach.el (org-attach-archive-delete-maybe): Don't query
about deleting attachments if the entry doesn't have any attachments.
---
 lisp/org-attach.el | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/lisp/org-attach.el b/lisp/org-attach.el
index 192815f4f..53389f782 100644
--- a/lisp/org-attach.el
+++ b/lisp/org-attach.el
@@ -574,10 +574,8 @@ (defun org-attach-archive-delete-maybe ()
   "Maybe delete subtree attachments when archiving.
 This function is called by `org-archive-hook'.  The option
 `org-attach-archive-delete' controls its behavior."
-  (when (if (eq org-attach-archive-delete 'query)
-   (yes-or-no-p "Delete all attachments? ")
- org-attach-archive-delete)
-(org-attach-delete-all t)))
+  (when org-attach-archive-delete
+(org-attach-delete-all (not (eq org-attach-archive-delete 'query)
 
 
 ;; Attach from dired.
-- 
2.18.0




[O] Bug: Archiving items with org-attach-archive-delete set to 'query' always asks for confirmation

2018-08-10 Thread Luciano Passuello
Hello,

When I set org-attach-archive-delete to query, Org is supposed to ask
me for confirmation when archiving entries with attachments. However,
I am always asked for confirmation,  regardless if the item has
attachments in the first place. This is to me clearly undesirable
behavior.

Looking at the source code for org-attach, at line 573, that's indeed
what code tells us.
https://code.orgmode.org/bzg/org-mode/src/master/lisp/org-attach.el

My uninformed suggestion is to call org-attach-delete-all without the
force parameter, using the confirmation code already in
org-attach-delete-all.

Unfortunately, I'm not skilled enough in Elisp or knowledgeable in Org
source code to provide a reasonable patch.

Thanks!



Re: [O] Bug: ordered lists that start at > 1 don't work? [9.1.13 (9.1.13-elpaplus @ /home/ag/.emacs.d/elpa/26.1/develop/org-plus-contrib-20180730/)]

2018-08-04 Thread Ag Ibragimov



Kaushal Modi  writes:

Oh it seems I misunderstood how it works, I thought the cookie 
should

be in the front, e.g.:

[@20]. item 20
  22. item 22
  etc.

but instead it should be

1. [@20] item 20

and after pressing M-RET it automatically replaces 1. with 20. 
Maybe the

documentation on this subject could be more elaborate.

Thank you,
Ag


Hello,

On Sat, Aug 4, 2018, 8:12 AM Ag Ibragimov 
 wrote:




According to the documentation:

> If you want a list to start with a different value (e.g., 
> 20), start

> the text of the item with [@20]

it doesn't seem to work for me. What am I missing?



What does not work?

1. Can you paste a minimal working example of your Org file that 
contains

the use of that syntax?
2. What are you exporting that file to (HTML, ASCII, ..)? AFAIK 
that syntax
is effective for only for exports and only if the exporter 
supports this.


Example: Export below to ascii:


1. Item 1.
2. [@10] Item 10.



--
Thanks,
Ag Ibragimov



Re: [O] Bug: ordered lists that start at > 1 don't work? [9.1.13 (9.1.13-elpaplus @ /home/ag/.emacs.d/elpa/26.1/develop/org-plus-contrib-20180730/)]

2018-08-04 Thread Kaushal Modi
Hello,

On Sat, Aug 4, 2018, 8:12 AM Ag Ibragimov  wrote:

>
> According to the documentation:
>
> > If you want a list to start with a different value (e.g., 20), start
> > the text of the item with [@20]
>
> it doesn't seem to work for me. What am I missing?


What does not work?

1. Can you paste a minimal working example of your Org file that contains
the use of that syntax?
2. What are you exporting that file to (HTML, ASCII, ..)? AFAIK that syntax
is effective for only for exports and only if the exporter supports this.

Example: Export below to ascii:


1. Item 1.
2. [@10] Item 10.
-- 

Kaushal Modi


[O] Bug: ordered lists that start at > 1 don't work? [9.1.13 (9.1.13-elpaplus @ /home/ag/.emacs.d/elpa/26.1/develop/org-plus-contrib-20180730/)]

2018-08-04 Thread Ag Ibragimov


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


According to the documentation:

> If you want a list to start with a different value (e.g., 20), start
> the text of the item with [@20]

it doesn't seem to work for me. What am I missing?

Emacs  : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
 of 2018-07-05
Package: Org mode version 9.1.13 (9.1.13-elpaplus @ 
/home/ag/.emacs.d/elpa/26.1/develop/org-plus-contrib-20180730/)

current state:
==
(setq
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-blank-before-new-entry nil
 org-babel-after-execute-hook '(spacemacs/ob-fix-inline-images)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-refile-targets '((nil :maxlevel . 3) (org-agenda-files :maxlevel . 3))
 org-enforce-todo-dependencies t
 org-use-property-inheritance t
 org-src-tab-acts-natively t
 org-imenu-depth 8
 org-download-annotate-function 'org-download-annotate-default
 org-agenda-files "~/Dropbox/org/.agenda-files"
 org-clock-report-include-clocking-task t
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-mode-hook '(er/add-org-mode-expansions abbrev-mode 
spacemacs/toggle-visual-line-navigation-on ag/org-mode-hook org-clock-load 
flyspell-mode spacemacs/org-setup-evil-surround
 spacemacs/delay-emoji-cheat-sheet-hook 
spacemacs/load-yasnippet toc-org-enable org-download-enable org-bullets-mode 
dotspacemacs//prettify-spacemacs-docs spacemacs//org-babel-do-load-languages
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-show-block-all append local] 5]
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-babel-show-result-all append local] 5] 
org-babel-result-hide-spec org-babel-hide-all-hashes spacemacs//evil-org-mode
 org-eldoc-load spacemacs//init-company-org-mode company-mode)
 org-clock-persist t
 org-outline-path-complete-in-steps nil
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-agenda-restore-windows-after-quit t
 org-confirm-elisp-link-function 'yes-or-no-p
 org-startup-with-inline-images t
 org-timer-done-hook '((lambda nil (hs-alert "-- timer done! --")))
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-bibtex-headline-format-function #[257 "\300.\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
 org-from-is-user-regexp "\\"
 org-babel-pre-tangle-hook '(save-buffer)
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-babel-load-languages '((emacs-lisp . t) (shell . t) (js . t) (clojure . t) 
(sql . t) (shell . t) (ditaa . t) (ruby . t))
 org-log-done t
 org-babel-post-tangle-hook '(ag/set-tangled-file-permissions)
 org-agenda-follow-indirect t
 org-ellipsis " ↴"
 org-list-demote-modify-bullet '(("+" . "-") ("-" . "+") ("*" . "+"))
 org-agenda-span 1
 org-fast-tag-selection-single-key t
 org-src-lang-modes '(("http" . "ob-http") ("ocaml" . tuareg) ("elisp" . 
emacs-lisp) ("ditaa" . artist) ("asymptote" . asy) ("dot" . fundamental) 
("sqlite" . sql) ("calc" . fundamental) ("C" . c) ("cpp" . c++)
  ("C++" . c++) ("screen" . shell-script) ("shell" . sh) 
("bash" . sh))
 org-catch-invisible-edits 'smart
 org-occur-hook '(org-first-headline-recenter)
 org-agenda-mode-hook '(override-evilified-keys)
 org-agenda-start-with-log-mode t
 org-log-into-drawer t
 org-ditaa-jar-path "/usr/share/java/ditaa/ditaa-0_10.jar"
 org-enforce-todo-checkbox-dependencies t
 org-structure-template-alist '(("sqlf" "#+begin_src sql :engine postgresql 
:cmdline \"-h localhost -U postgres -p 5434 -d 
finops_admin_development\"\n?\n#+end_src") ("s" "#+begin_src ?\n\n#+end_src")
("e" "#+begin_example\n?\n#+end_example") ("q" 
"#+begin_quote\n?\n#+end_quote") ("v" "#+begin_verse\n?\n#+end_verse") ("V" 
"#+begin_verbatim\n?\n#+end_verbatim")
("c" "#+begin_center\n?\n#+end_center") ("C" 
"#+begin_comment\n?\n#+end_comment") ("l" "#+begin_export 
latex\n?\n#+end_export") ("L" "#+latex: ")
("h" "#+begin_export html\n?\n#+end_export") 
("H" "#+html: ") ("a" "#+begin_export ascii\n?\n#+end_export") ("A" "#+ascii: 
") ("i" "#+index: ?") ("I" "#+include: %file ?"))
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers 
org-cycle-show-empty-lines org-optimize-window-after-visibility-change)
 org-todo-keywords '((sequence "TODO" "ONGOING" 

Re: [O] [bug] refiling puts random stuff in kill ring

2018-08-03 Thread Charles Millar




On 08/03/2018 08:21 PM, Samuel Wales wrote:

recent maint.

i kill with c-m-k, then move point, then refile an entry.  then i
yank.  that produces something that was earlier killed.

i expected what i killed.
I noticed this behavior two or three days ago (best as I remember), 
using M-w and C-w then C-y. I thought I was at fault, i.e. not hitting 
the correct keys. Also, it does not seem to occur consistently.


Org mode version 9.1.13 (release_9.1.13-895-gf79545 @ 
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 48, x86_64-pc-linux-gnu, GTK+ Version 3.22.29) 
of 2018-06-29


Charlie Millar



[O] [bug] refiling puts random stuff in kill ring

2018-08-03 Thread Samuel Wales
recent maint.

i kill with c-m-k, then move point, then refile an entry.  then i
yank.  that produces something that was earlier killed.

i expected what i killed.

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.



Re: [O] BUG in ob-scheme WAS: Re: Babel: verbatim results yield a table

2018-08-03 Thread Jarmo Hurri


Greetings again.

"Berry, Charles"  writes:

>> The org manual states that in the :results header argument of a block
>> 
>> verbatim Interpret literally and insert as quoted text. Do not create a
>> table. Usage example: :results value verbatim
>
> Unfortunately, `org-babel-scheme--table-or-string' does not honor
> :results verbatim. :-(

I wrote a patch for this before realizing that it had already been fixed
in the master branch (I was running the stable branch).

This should teach me a lesson again... :-)

Jarmo




Re: [O] BUG in ob-scheme WAS: Re: Babel: verbatim results yield a table

2018-08-03 Thread Jarmo Hurri
"Berry, Charles"  writes:

>> The org manual states that in the :results header argument of a block
>> 
>> verbatim Interpret literally and insert as quoted text. Do not create a
>> table. Usage example: :results value verbatim
>
> Unfortunately, `org-babel-scheme--table-or-string' does not honor
> :results verbatim. :-(

Thanks, I did not have the guts to call it a bug.

I'll see if I could provide a patch for this later.

Thanks.

Jarmo




[O] BUG in ob-scheme WAS: Re: Babel: verbatim results yield a table

2018-08-02 Thread Berry, Charles



> On Aug 2, 2018, at 5:19 AM, Jarmo Hurri  wrote:
> 
> 
> Greetings.
> 
> The org manual states that in the :results header argument of a block
> 
> verbatim Interpret literally and insert as quoted text. Do not create a
> table. Usage example: :results value verbatim

Unfortunately, `org-babel-scheme--table-or-string' does not honor :results 
verbatim. :-(


> 
> The quote above is from https://orgmode.org/manual/results.html
> 
> Given this description, I am trying to understand the result below from
> a Scheme snippet (this is an exercise in the good old SICP). In
> particular, why is the table created from the (nested) list?
> 
> Jarmo
> 
>   #+BEGIN_SRC scheme :exports both :results value verbatim
> (define (deep-reverse lst)
>   (define (deep-iter lst result)
> (if (null? lst)
> result
> (let ((first (car lst)) (rest (cdr lst)))
>   (deep-iter rest
>  (cons (if
> (pair? first)
> (deep-reverse first)
> first)
>result)
>   (deep-iter lst '()))
> 
> (deep-reverse (list (list 1 2 3 4) (list (list 5 6) 7 8)))
>   #+END_SRC
> 
>   #+RESULTS:
>   | 8 | 7 | (6 5) |   |
>   | 4 | 3 | 2 | 1 |
> 

HTH,

Chuck





[O] Bug: tags-emoji-alignment [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/local/Cellar/emacs/26.1_1/share/emacs/26.1/lisp/org/)]

2018-08-01 Thread Will Pierce
This might be out of scope for the org list, but the excellent emojify-mode
(https://github.com/iqbalansari/emacs-emojify) breaks the alignment of org
tags when emojies are included in the headings.

So:

```
** TODO write something short :writing:
```

but

```
** TODO :waving_black_flag: write something short  :writing:
```

Emacs  : GNU Emacs 26.1 (build 1, x86_64-apple-darwin17.5.0, NS
appkit-1561.40 Version 10.13.4 (Build 17E199))
 of 2018-06-13
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/usr/local/Cellar/emacs/26.1_1/share/emacs/26.1/lisp/org/)


[O] Bug: truncate lines when setupfile [9.0.5 (9.0.5-elpa @ /home/xavier/.emacs.d/elpa/org-20170210/)]

2018-07-30 Thread Xavier Leleu
Hi,
The default truncate-line option turns off when the org-file contains a 
#+SETUPFILE: mysetupfile.setup. M-x toggle-truncate-lines gets truncation back. 



Emacs  : GNU Emacs 24.4.1 (i586-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2017-09-12 on x86-csail-01, modified by Debian
Package: Org mode version 9.0.5 (9.0.5-elpa @ 
/home/xavier/.emacs.d/elpa/org-20170210/)




[O] Bug: Variable comment-start-skip in the function org-agenda-skip is nil but should be a string. [9.1.13 (9.1.13-elpa @ ~/.emacs.d/elpa/org-20180716/)]

2018-07-30 Thread Pierre-Henry F.
Hello dear list and thank you for looking at this stuff down below as
well as org-mode and many other things.

Best,
PHF

I get:

  Debugger entered--Lisp error: (wrong-type-argument stringp nil)

looking-at(nil)

org-agenda-skip()

org-scan-tags(proposition_org/if_proposition_then_get_content_else_nil t 
nil nil)

org-map-entries(proposition_org/if_proposition_then_get_content_else_nil t)

(seq-filter 'not (org-map-entries 
'proposition_org/if_proposition_then_get_content_else_nil t))

proposition_org/list_propositions_in_buffer()

(progn (insert-file-contents file_name) 
(proposition_org/list_propositions_in_buffer))

(unwind-protect (progn (insert-file-contents file_name) 
(proposition_org/list_propositions_in_buffer)) (and (buffer-name temp-buffer) 
(kill-buffer temp-buffer)))

(save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn 
(insert-file-contents file_name) (proposition_org/list_propositions_in_buffer)) 
(and (buffer-name temp-buffer) (kill-buffer temp-buffer

(let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-buffer 
(set-buffer temp-buffer) (unwind-protect (progn (insert-file-contents 
file_name) (proposition_org/list_propositions_in_buffer)) (and (buffer-name 
temp-buffer) (kill-buffer temp-buffer)

(cond ((file-exists-p file_name) (let ((temp-buffer (generate-new-buffer " 
*temp*"))) (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn 
(insert-file-contents file_name) (proposition_org/list_propositions_in_buffer)) 
(and (buffer-name temp-buffer) (kill-buffer temp-buffer)) (t 'nil))

(let ((file_name (expand-file-name x))) (cond ((file-exists-p file_name) 
(let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-buffer 
(set-buffer temp-buffer) (unwind-protect (progn (insert-file-contents 
file_name) (proposition_org/list_propositions_in_buffer)) (and (buffer-name 
temp-buffer) (kill-buffer temp-buffer)) (t 'nil)))

proposition_org/extract_posts("~/tmp.org")

(message (proposition_org/extract_posts "~/tmp.org"))

eval((message (proposition_org/extract_posts "~/tmp.org")) nil)

elisp--eval-last-sexp(nil)

eval-last-sexp(nil)

funcall-interactively(eval-last-sexp nil)

call-interactively(eval-last-sexp nil nil)

command-execute(eval-last-sexp)

By executing this program:

  ;; Import

  (require 'seq)

  (require 'cl-lib)

  (require 'org)

  ;; Define

  (defun proposition_org/extract_posts (x)

"file_name → [proposition_org]"

(let ((file_name (expand-file-name x)))

  (cond ((file-exists-p file_name)

 (with-temp-buffer

   (insert-file-contents file_name)

   (proposition_org/list_propositions_in_buffer)))

(t '()

  (defun proposition_org/list_propositions_in_buffer ()

"current_buffer → [proposition_org]"

(seq-filter 'not (org-map-entries 
'proposition_org/if_proposition_then_get_content_else_nil t)))

  (defun proposition_org/if_proposition_then_get_content_else_nil ()

"current_heading → nil | proposition_org"

(cond ((proposition_org/is_publication) (proposition_org/get_content))

  (t nil)))

  (defun proposition_org/get_content ()

"current_heading → string"

(org-narrow-to-subtree)

(let ((content (buffer-string)))

  (widen)

  content))

  (defun proposition_org/is_publication ()

"current_heading → boolean"

(eq (proposition_org/is_proposition_properties (org-entry-properties)) 
'true))

  (defun proposition_org/is_proposition_properties (properties)

"properties ≡ [[key,value]]

 properties → 'true | 'false"

(let ((proposition_properties_pattern

   (list

(cons

 (lambda (x) (equal "PUBLIC" x))

 (lambda (x) (equal "true" x)))

(cons

 (lambda (x) (equal "TARGET_ID" x))

 (lambda (x) (stringp x)))

(cons

 (lambda (x) (equal "PREVIOUS_VERSION" x))

 (lambda (x) (stringp x)))

(cons

 (lambda (x) (equal "AUTHOR" x))

 (lambda (x) (stringp x)))

(cons

 (lambda (x) (equal "TYPE_NAME" x))

 (lambda (x) (equal "proposition_org" x)))

(cons

 (lambda (x) (equal "TYPE_ID" x))

 (lambda (x) (equal "af7658fc-0541-4cbe-8a5c-04fd5cde74ff" x))

  (proposition_org/properties_has_pattern properties 
proposition_properties_pattern)))

  (defun proposition_org/properties_has_pattern (properties patterns  
result)

"properties ≡ [[key,value]]

 patterns ≡ [[predicate,predicate]]

 properties patterns → 'true | 'false"

(proposition_org/to_truth

 (cond ((null result) (proposition_org/properties_has_pattern properties 
patterns 'true))

   ((eq result 'false) result)

   ((null patterns) result)

   (t (proposition_org/properties_has_pattern

  

[O] Bug: Broken link in documentation

2018-07-30 Thread Julien Palard
Hi,

I'm new to Org mode and spotted a broken link at the bottom of 
https://orgmode.org/features.html : mobileorg.ncogni.to

$ curl -s https://orgmode.org/features.html | grep 
http://mobileorg.ncogni.to/
Richard Moreland has developed http://mobileorg.ncogni.to/;>MobileOrg, a free software for iPhone and
$ curl -i mobileorg.ncogni.to
curl: (6) Could not resolve host: mobileorg.ncogni.to

Bests,
​-- 
Julien Palard
https://mdk.fr​





[O] Bug: org-indent-boundary-char doesn't have org-indent face [9.1.9 (release_9.1.9-65-g5e4542 @ c:/Program Files/emacs-26.1-x86_64/share/emacs/26.1/lisp/org/)]

2018-07-30 Thread HIRATA Tadashi
Hello org-mode developers,

I found a bug that org-indent-boundary-char doens't have
org-indent face property in org-indent-mode. This causes an
appearance issue when you use org-mode with whitespace-mode
that you can't control org-indent-boundary-char's face
neither whitespace-space face nor org-indent face.

Here is a quick patch to fix the problem. (though I test it
in 9.1.9, but it should work well in the latest version).

Sincerely,
Tadashi



diff -u org-indent.el_org org-indent.el
--- org-indent.el_org   2018-07-23 14:13:06.045078400 +0900
+++ org-indent.el   2018-07-24 10:00:57.898200400 +0900
@@ -150,10 +150,11 @@
   ;; Text line prefixes.
   (aset org-indent--text-line-prefixes
n
-   (concat (org-add-props (make-string (+ n indentation) ?\s)
-   nil 'face 'org-indent)
-   (and (> n 0)
-(char-to-string org-indent-boundary-char)))
+   (org-add-props 
+   (concat (make-string (+ n indentation) ?\s)
+   (and (> n 0)
+(char-to-string org-indent-boundary-char)))
+   nil 'face 'org-indent)
 
 (defsubst org-indent-remove-properties (beg end)
   "Remove indentations between BEG and END."





Emacs  : GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
 of 2018-05-31
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ c:/Program 
Files/emacs-26.1-x86_64/share/emacs/26.1/lisp/org/)

current state:
==
(setq
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-time-stamp-custom-formats '("<%Y/%m/%d>" . "<%Y/%m/%d %H:%M>")
 org-indent-boundary-char 124
 org-mode-hook '(#[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-show-block-all append
local]
   5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-babel-show-result-all
append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes
 (lambda nil (setq truncate-lines nil)
  (define-key org-mode-map "\346" (quote org-metaright))
  (define-key org-mode-map "\342" (quote org-metaleft))
  (define-key org-mode-map "\360" (quote org-metaup))
  (define-key org-mode-map "\356" (quote org-metadown))
  (define-key org-mode-map "\306" (quote org-shiftmetaright))
  (define-key org-mode-map "\302" (quote org-shiftmetaleft))
  (define-key org-mode-map "\320" (quote org-shiftmetaup))
  (define-key org-mode-map "\316" (quote org-shiftmetadown))
  (set-face-foreground (quote org-level-1) "DeepSkyBlue")
  (set-face-foreground (quote org-level-2) "MediumBlue")
  (set-face-foreground (quote org-level-3) "DodgerBlue")
  (set-face-foreground (quote org-level-4) "SlateBlue")
  (set-face-foreground (quote org-level-5) "LightSeaGreen")
  (set-face-foreground (quote org-level-6) "DarkGreen")
  (set-face-foreground (quote org-level-7) "gray40")
  (set-face-foreground (quote org-level-8) "gray60")
  (set-face-foreground (quote org-indent) "gray100"))
 )
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-startup-indented t
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
 org-babel-pre-tangle-hook '(save-buffer)
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-hide-leading-stars t
 org-occur-hook '(org-first-headline-recenter)
 org-cycle-separator-lines 0
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-speed-command-hook '(org-speed-command-activate
  org-babel-speed-command-activate)
 org-confirm-shell-link-function 'yes-or-no-p
 org-link-parameters '(("id" :follow org-id-open)
   ("rmail" :follow org-rmail-open :store
org-rmail-store-link)
   ("mhe" :follow org-mhe-open :store org-mhe-store-link)
   ("irc" :follow 

Re: [O] Bug: Variable comment-start-skip in the function org-agenda-skip is nil but should be a string. [9.1.13 (9.1.13-elpa @ ~/.emacs.d/elpa/org-20180716/)]

2018-07-21 Thread Pierre-Henry F.
Ok, I found how to correct it:

(defun proposition_org/extract_posts (x)
  "file_name → [proposition_org]"
  (let ((file_name (expand-file-name x)))
(cond ((file-exists-p file_name)
   (with-temp-buffer
 (insert-file-contents file_name)
 (org-mode)  ;; <--- THIS IS WHAT WAS MISSING
 (proposition_org/list_propositions_in_buffer)))
  (t '()
Best,
PHF

‐‐‐ Original Message ‐‐‐
On July 21, 2018 6:28 PM, Pierre-Henry F.  wrote:

> Hello dear list and thank you for looking at this stuff down below as
> well as org-mode and many other things.
>
> Best,
> PHF
>
> I get:
>
>   Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> looking-at(nil)
> org-agenda-skip()
> org-scan-tags(proposition_org/if_proposition_then_get_content_else_nil t 
> nil nil)
> org-map-entries(proposition_org/if_proposition_then_get_content_else_nil 
> t)
> (seq-filter 'not (org-map-entries 
> 'proposition_org/if_proposition_then_get_content_else_nil t))
> proposition_org/list_propositions_in_buffer()
> (progn (insert-file-contents file_name) 
> (proposition_org/list_propositions_in_buffer))
> (unwind-protect (progn (insert-file-contents file_name) 
> (proposition_org/list_propositions_in_buffer)) (and (buffer-name temp-buffer) 
> (kill-buffer temp-buffer)))
> (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn 
> (insert-file-contents file_name) 
> (proposition_org/list_propositions_in_buffer)) (and (buffer-name temp-buffer) 
> (kill-buffer temp-buffer
> (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-buffer 
> (set-buffer temp-buffer) (unwind-protect (progn (insert-file-contents 
> file_name) (proposition_org/list_propositions_in_buffer)) (and (buffer-name 
> temp-buffer) (kill-buffer temp-buffer)
> (cond ((file-exists-p file_name) (let ((temp-buffer (generate-new-buffer 
> " *temp*"))) (save-current-buffer (set-buffer temp-buffer) (unwind-protect 
> (progn (insert-file-contents file_name) 
> (proposition_org/list_propositions_in_buffer)) (and (buffer-name temp-buffer) 
> (kill-buffer temp-buffer)) (t 'nil))
> (let ((file_name (expand-file-name x))) (cond ((file-exists-p file_name) 
> (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-buffer 
> (set-buffer temp-buffer) (unwind-protect (progn (insert-file-contents 
> file_name) (proposition_org/list_propositions_in_buffer)) (and (buffer-name 
> temp-buffer) (kill-buffer temp-buffer)) (t 'nil)))
> proposition_org/extract_posts("~/tmp.org")
> (message (proposition_org/extract_posts "~/tmp.org"))
> eval((message (proposition_org/extract_posts "~/tmp.org")) nil)
> elisp--eval-last-sexp(nil)
> eval-last-sexp(nil)
> funcall-interactively(eval-last-sexp nil)
> call-interactively(eval-last-sexp nil nil)
> command-execute(eval-last-sexp)
>
> By executing this program:
>
>   ;; Import
>
>   (require 'seq)
>   (require 'cl-lib)
>   (require 'org)
>
>   ;; Define
>
>   (defun proposition_org/extract_posts (x)
> "file_name → [proposition_org]"
> (let ((file_name (expand-file-name x)))
>   (cond ((file-exists-p file_name)
>  (with-temp-buffer
>(insert-file-contents file_name)
>(proposition_org/list_propositions_in_buffer)))
> (t '()
>
>   (defun proposition_org/list_propositions_in_buffer ()
> "current_buffer → [proposition_org]"
>
> (seq-filter 'not (org-map-entries 
> 'proposition_org/if_proposition_then_get_content_else_nil t)))
>
>   (defun proposition_org/if_proposition_then_get_content_else_nil ()
> "current_heading → nil | proposition_org"
> (cond ((proposition_org/is_publication) (proposition_org/get_content))
>   (t nil)))
>
>   (defun proposition_org/get_content ()
> "current_heading → string"
> (org-narrow-to-subtree)
> (let ((content (buffer-string)))
>   (widen)
>   content))
>
>   (defun proposition_org/is_publication ()
> "current_heading → boolean"
> (eq (proposition_org/is_proposition_properties (org-entry-properties)) 
> 'true))
>
>   (defun proposition_org/is_proposition_properties (properties)
> "properties ≡ [[key,value]]
>
>  properties → 'true | 'false"
>
> (let ((proposition_properties_pattern
>(list
> (cons
>  (lambda (x) (equal "PUBLIC" x))
>  (lambda (x) (equal "true" x)))
>
> (cons
>  (lambda (x) (equal "TARGET_ID" x))
>  (lambda (x) (stringp x)))
>
> (cons
>  (lambda (x) (equal "PREVIOUS_VERSION" x))
>  (lambda (x) (stringp x)))
>
> (cons
>  (lambda (x) (equal "AUTHOR" x))
>  (lambda (x) (stringp x)))
>
> (cons
>  (lambda (x) (equal "TYPE_NAME" x))
>  (lambda (x) (equal "proposition_org" x)))
>
> (cons
>  

Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-19 Thread Sebastian Reuße


Heikki Lehvaslaiho  writes:

> (string-collate-lessp "ß" "ssa" "de_DE.utf-8") ; nil
> (string-lessp "ß" "ssa")   ; nil

This shows us that your Emacs installation does not support alphabetic
sorting at all, regardless of case, and instead only sorts
lexicographically (i.e., regardless of locale). This likely happens due
to your platform not implementing wide characters in terms of ISO 10646.
It is likely not related to your language environment, because the
implementation of ‘string-collate-lessp’ ignores the language
environment when a locale string is passed.

Kind regards,
SR

-- 
Insane cobra split the wood
Trader of the lowland breed
Call a jittney, drive away
In the slipstream we will stay



Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-19 Thread Heikki Lehvaslaiho
My emacs is from homebrew without any manual settings on locale. I assume a
number of locale settings come with it. I have not had any problems before
this.

OS X does not have LANG envvar set. This computer came with Finnish
language set and I switched to English (Australian) for interface. This has
lead to somewhat weird locale setting at OS:

$ defaults read .GlobalPreferences AppleLanguages
(
"en-FI"
)

Apart from ssa, the output from string-collate-lessp seems to be what is to
be expected:

(string-collate-lessp "a" "x" "de_DE.utf-8" nil) ; t
(string-collate-lessp "a" "X" "de_DE.utf-8" nil) ; nil
(string-collate-lessp "ß" "ssa" "de_DE.utf-8") ; nil
(string-lessp "ß" "ssa")   ; nil
(string-collate-lessp "ä" "ö" "fi_FI.utf-8") ; t
(string-collate-lessp "Ä" "ö" "fi_FI.utf-8") ; t

I can not able to comment on C code, but it really seems that alphabetic
sorting is fixed to case-sensitive mode.




 -Heikki

Heikki Lehväslaiho - skype:heikki_lehvaslaiho cell: +358 40 850 6640
http://about.me/heikki

On 17 July 2018 at 09:59, Sebastian Reuße  wrote:

>
> Heikki Lehvaslaiho  writes:
>
> > x86_64-apple-darwin14.5.0
>
> Looking at the C source of ‘string-collate-lessp’ (src/fns.c), it looks
> like there exists a case where Emacs itself will fall back on
> ‘string-lessp’ even when ‘string-collate-lessp’ is invoked.
>
> #else  /* !__STDC_ISO_10646__, !WINDOWSNT */
>  return Fstring_lessp (s1, s2);
> #endif /* !__STDC_ISO_10646__, !WINDOWSNT */
>
> I can’t tell what the first macro evaluates to on your platform. Might
> this be the cause?
>
> An indication for whether your Emacs uses the locale at all may be
> testing the following (presuming you have the German locale data
> installed and compiled):
>
> (string-collate-lessp "ß" "ssa" "de_DE.utf-8") ; t
> (string-lessp "ß" "ssa")   ; nil
>
> This is based on the German ‘ß’ ligature being sorted as if it were
> equal to the string ‘ss’ (you can probably construct something analogous
> using fi_FI). If the first call returns nil, your Emacs isn’t using the
> locale data at all.
>
> Kind regards,
> SR
>
> --
> Insane cobra split the wood
> Trader of the lowland breed
> Call a jittney, drive away
> In the slipstream we will stay
>


[O] [Bug] org-attach-set-directory

2018-07-18 Thread Florian Lindner
Hello,

doing C-a s  on an entry with an existing attachement produces

make-directory: Die Datei existiert bereits: /home/florian/test/data/

(translation: File already exists)

Actually, I implemented this functionality with the help of Nicolas Goaziou, 
but it seems an org mode or emacs upgrade broke it.

I will try to debug that further, but right now, my time is very limited, only 
undershot by my elisp knowledge.

Maybe someone can more quickly fix that... ;-)

Best,
Florian

Backtrace:

Debugger entered--Lisp error: (file-already-exists "Die Datei existiert 
bereits" "/home/florian/test/mydata")
  make-directory-internal("/home/florian/test/mydata")
  make-directory("/home/florian/test/mydata" nil)
  
copy-directory("/home/florian/test/data/c1/32d552-b7bb-43b1-b0d8-c57c00d61f9b" 
"/home/florian/test/mydata" t nil t)
  org-attach-set-directory(nil)
  funcall-interactively(org-attach-set-directory nil)
  call-interactively(org-attach-set-directory)
  org-attach()
  funcall-interactively(org-attach)
  call-interactively(org-attach nil nil)
  command-execute(org-attach)

Org mode version 9.1.13 (9.1.13-elpa @ 
/home/florian/.emacs.d/elpa/org-20180716/)





Re: [O] [BUG] org-special-ctrl-k no longer protects tags

2018-07-17 Thread Nicolas Goaziou
Hello,

Matt Lundin  writes:

> Since commit e87ebca2a7, setting org-special-ctrl-k to t no longer
> protects tags if when pressing C-k (org-kill-line) in the middle of a
> headline. The expected behavior is described in the docstring for
> org-special-ctrl-k: "When in the middle of the headline text, kill the
> headline up to the tags."
>
> Take the following example:
>
> * Headline  :tag:
>
> If I hit C-k with the cursor on the letter "l" on the example above, I
> expect to get this...
>
> * Head  :tag:
>
> Instead, I get this...
>
> * Head

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



[O] [BUG] org-special-ctrl-k no longer protects tags

2018-07-17 Thread Matt Lundin
Since commit e87ebca2a7, setting org-special-ctrl-k to t no longer
protects tags if when pressing C-k (org-kill-line) in the middle of a
headline. The expected behavior is described in the docstring for
org-special-ctrl-k: "When in the middle of the headline text, kill the
headline up to the tags."

Take the following example:

* Headline  :tag:

If I hit C-k with the cursor on the letter "l" on the example above, I
expect to get this...

* Head  :tag:

Instead, I get this...

* Head

I think this is because when (looking-at org-tag-line-re) is called on
line 22840, the cursor is in the middle of the line, whereas
org-tag-line-re expects it to be at the beginning of the line.

Best,
Matt



Re: [O] Bug: (org-clock-in 4) fails from non-Org buffer due to nil org-complex-heading-regexp [9.1.13 (9.1.13-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20180702/)]

2018-07-17 Thread Nicolas Goaziou
Hello,

Robert Irelan  writes:

> How to reproduce:
>
> 1. Clock into default task.
> 2. Switch to non-Org buffer (I used `*scratch*`).
> 3. Type C-u M-x org-clock-info
> 4. Type d to clock into default task (which is located in a buffer
>that's part of my agenda).
>
> Clocking in will then fail with the attached backtrace. It appears that
> this is happening due to a missing value for the variable
> `org-complex-heading-regexp`. Clocking in from an Org mode buffer
> works. I'd expect that org-clock-in would attempt to temporarily switch
> to that buffer to correctly set these buffer-local variables.
>
> Backtrace:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   looking-at(nil)
>   org-heading-components()
>   org-clock-in((4))

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-17 Thread Sebastian Reuße


Heikki Lehvaslaiho  writes:

> x86_64-apple-darwin14.5.0

Looking at the C source of ‘string-collate-lessp’ (src/fns.c), it looks
like there exists a case where Emacs itself will fall back on
‘string-lessp’ even when ‘string-collate-lessp’ is invoked.

#else  /* !__STDC_ISO_10646__, !WINDOWSNT */
 return Fstring_lessp (s1, s2);
#endif /* !__STDC_ISO_10646__, !WINDOWSNT */

I can’t tell what the first macro evaluates to on your platform. Might
this be the cause?

An indication for whether your Emacs uses the locale at all may be
testing the following (presuming you have the German locale data
installed and compiled):

(string-collate-lessp "ß" "ssa" "de_DE.utf-8") ; t
(string-lessp "ß" "ssa")   ; nil

This is based on the German ‘ß’ ligature being sorted as if it were
equal to the string ‘ss’ (you can probably construct something analogous
using fi_FI). If the first call returns nil, your Emacs isn’t using the
locale data at all.

Kind regards,
SR

-- 
Insane cobra split the wood
Trader of the lowland breed
Call a jittney, drive away
In the slipstream we will stay



Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-17 Thread Heikki Lehvaslaiho
Thanks for replies,

I am using:
GNU Emacs 26.1 (build 1, x86_64-apple-darwin14.5.0, NS appkit-1348.17
Version 10.10.5 (Build 14F2511)) of 2018-05-31


This is what I get:

(string-collate-lessp "a" "x" "de_DE.utf-8" nil) ; t
(string-collate-lessp "a" "X" "de_DE.utf-8" t) ; nil
(string-collate-lessp "a" "x" "fi_FI.utf-8" nil) ; t
(string-collate-lessp "a" "X" "fi_FI.utf-8" t) ; nil


I think I have lost the sense how Emacs language environments work
after struggling for years with buffers getting automatically
converted to Latin-1. I started setting all possible variables to
'UTF-8 and finally something did it.

Now I tried again various values to see if they affect the org table
sorting:

(set-language-environment 'utf-8)
(set-language-environment 'English)
(set-language-environment 'Swedish)

(setq locale-coding-system 'utf-8)
(setq locale-coding-system 'fi_FI.utf-8)
(setq locale-coding-system 'de_DE.utf-8)
(setq locale-coding-system 'en_GB.utf-8)

Unfortunately none of these made any difference. Any suggestions?

I am testing sorting in a simple one column table:

| a |
| c |
| B |
| D |




 -Heikki

Heikki Lehväslaiho - skype:heikki_lehvaslaiho cell: +358 40 850 6640
http://about.me/heikki

On 14 July 2018 at 15:31, Sebastian Reuße  wrote:

> Hello Nicolas, hello Heikki,
>
> > Heikki Lehvaslaiho  writes:
>
> >> I can not see any change in function with the new code. Alphabetical
> >> sorting is fixedly case sensitive.
>
> Is your Emacs≤24? Emacs (surprisingly) only gained a facility for
> alphabetic (locale-sensitive) sorting with ver. 25. Before that, we will
> resort to using «string-lessp», which only sorts lexicographically (i.e,
> based on the binary character value, which means it is always
> case-sensitive on Unicode systems).
>
> If you are using GNU Emacs≥25, what locale are you using? FI_fi and most
> of the other western locales are based on ISO-14651, so you should
> always get case-*in*sensitive orderings, which is what I get with Emacs
> 26.1. So, evaluating the following should all yield «t»:
>
> (string-collate-lessp "a" "x" "de_DE.utf-8" nil)
> (string-collate-lessp "a" "X" "de_DE.utf-8" t)
> (string-collate-lessp "a" "x" "fi_FI.utf-8" nil)
> (string-collate-lessp "a" "X" "fi_FI.utf-8" t)
>
> Kind regards,
>
> Sebastian
>
> --
> Insane cobra split the wood
> Trader of the lowland breed
> Call a jittney, drive away
> In the slipstream we will stay
>


[O] Bug: (org-clock-in 4) fails from non-Org buffer due to nil org-complex-heading-regexp [9.1.13 (9.1.13-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20180702/)]

2018-07-16 Thread Robert Irelan
How to reproduce:

1. Clock into default task.
2. Switch to non-Org buffer (I used `*scratch*`).
3. Type C-u M-x org-clock-info
4. Type d to clock into default task (which is located in a buffer
   that's part of my agenda).

Clocking in will then fail with the attached backtrace. It appears that
this is happening due to a missing value for the variable
`org-complex-heading-regexp`. Clocking in from an Org mode buffer
works. I'd expect that org-clock-in would attempt to temporarily switch
to that buffer to correctly set these buffer-local variables.

Backtrace:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  looking-at(nil)
  org-heading-components()
  org-clock-in((4))
  funcall-interactively(org-clock-in (4))
  #(org-clock-in record nil)
  apply(# org-clock-in (record nil))
  call-interactively@ido-cr+-record-current-command(# org-clock-in record nil)
  apply(call-interactively@ido-cr+-record-current-command # (org-clock-in record nil))
  call-interactively(org-clock-in record nil)
  command-execute(org-clock-in record)
  #f(compiled-function (cmd) #)("org-clock-in")
  ivy-call()
  ivy-read("C-u M-x " ("bh/punch-in" "org-clock-in"
"toggle-debug-on-error" "org-reload" ...) :predicate nil
:require-match t :history counsel-M-x-history :action
#f(compiled-function (cmd) #) :sort nil :keymap
(keymap (67108908 . counsel--info-lookup-symbol) (67108910 .
counsel-find-symbol)) :initial-input nil :caller counsel-M-x)
  counsel-M-x()
  funcall-interactively(counsel-M-x)
  #(counsel-M-x nil nil)
  apply(# counsel-M-x (nil nil))
  call-interactively@ido-cr+-record-current-command(# counsel-M-x nil nil)
  apply(call-interactively@ido-cr+-record-current-command # (counsel-M-x nil nil))
  call-interactively(counsel-M-x nil nil)
  command-execute(counsel-M-x)

Emacs  : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.22.24), modified by Debian
Package: Org mode version 9.1.13 (9.1.13-elpaplus @
~/.emacs.d/elpa/org-plus-contrib-20180702/)

current state:
==
(setq
 org-ref-notes-directory "~/Documents/org/home-org"
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-refile-target-verify-function 'bh/verify-refile-target
 org-after-todo-state-change-hook
'(org-buganizer-after-todo-state-change-hook org-clock-out-if-current)
 org-columns-default-format "%60ITEM(Task) %10Effort(Effort){:}
%10CLOCKSUM %10CLOCKSUM_T"
 org-drill-adjust-intervals-for-early-and-late-repetitions-p t
 org-agenda-sticky t
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-protocol-default-template-key "p"
 org-global-properties '(("Effort_ALL" . "0:05 0:10 0:15 0:30 0:45
1:00 2:00 3:00 4:00 5:00 6:00 8:00")
 ("SYTLE_ALL" . "habit"))
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer bh/clock-out-maybe)
 org-refile-targets '((nil :maxlevel . 9) (org-agenda-files :maxlevel . 9))
 org-html-format-inlinetask-function
'org-html-format-inlinetask-default-function
 org-pretty-entities t
 org-enforce-todo-dependencies t
 org-drill-right-cloze-delimiter "|!"
 org-ref-create-notes-hook '((lambda nil (org-narrow-to-subtree)
  (insert (format "cite:%s\n"
(org-entry-get (point) "Custom_ID"
 )
 org-odt-format-headline-function 'org-odt-format-headline-default-function
 org-special-ctrl-a/e t
 org-agenda-files "~/.emacs.d/agenda_files"
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-clock-report-include-clocking-task t
 org-log-redeadline 'time
 org-ref-pdf-directory "~/Documents/org/home-org/lib/"
 org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
 org-id-link-to-org-use-id t
 org-mode-hook '(org-ref-org-menu org-clock-load
 #[0 "\300\301\302\303\304$\207" [add-hook
change-major-mode-hook org-show-block-all append local] 5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook
org-babel-show-result-all append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes
org-eldoc-load)
 org-clock-persist t
 org-ref-insert-cite-function 'org-ref-helm-insert-cite-link
 org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
 org-outline-path-complete-in-steps nil
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-startup-indented t
 org-clock-history-length 23
 org-ref-clean-bibtex-key-function '(lambda (key)
(replace-regexp-in-string ":" "" key))
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-clock-frame-title-format '("" "%b - " org-mode-line-string)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-bibtex-headline-format-function #[257 "\300 \236A\207" [:title] 3
"\n\n(fn ENTRY)"]
 org-adapt-indentation nil
 org-log-reschedule 'time
 org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
 org-agenda-text-search-extra-files 

Re: [O] Bug: Table does not align properly [9.1.13 (9.1.13-elpaplus @ /home/diogo/.emacs.d/elpa/org-plus-contrib-20180521/)]

2018-07-14 Thread Diogo Ferrari
Yes, I tried the development version in that website. I believe
org-plus-contrib can be the issue. It is not working properly. It is
messing with table formatting a lot when I use <> to reduce the size of the
column. It works even worse with links of the type [[link][link label]] and
when I use org table edit field (C-c `) to edit the cell in a separate
window. When I go back from table edit field, it looses the alignment and
to get it back I need to either reopen the file or use the table edit field
again. I am using now the version 9.0.9 (org-plus-contrib-20170702), which
at least it does not mess with the alignment as much. The links, however,
still does not align properly. If I run emacs -Q, the alignment works
perfect, even with links. I use some features of org and org-plus-contrib,
so I will keep trying a little more. Sorry for not contributing more to fix
it. Maybe I at some point I will go over the .el files to try to figure out
what is going on.

On Sat, Jul 14, 2018 at 8:00 AM Nicolas Goaziou 
wrote:

> Diogo Ferrari  writes:
>
> > from github, The version there is 9.13.1 and the problem remains
>
> We don't use Github. You can find development version here:
> https://code.orgmode.org/bzg/org-mode
>
>

-- 
Diogo Ferrari
PhD Candidate
University of Michigan, Ann Arbor
Department of Political Science
E-mail: dferr...@umich.edu
Website: http://dioferrari.wordpress.com/

Open Source! Use R! Use Linux! Use Emacs! Use Python!

"A vida é a arte de tirar conclusões suficientes de dados insuficientes"


Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-14 Thread Sebastian Reuße
Hello Nicolas, hello Heikki,

> Heikki Lehvaslaiho  writes:

>> I can not see any change in function with the new code. Alphabetical
>> sorting is fixedly case sensitive.

Is your Emacs≤24? Emacs (surprisingly) only gained a facility for
alphabetic (locale-sensitive) sorting with ver. 25. Before that, we will
resort to using «string-lessp», which only sorts lexicographically (i.e,
based on the binary character value, which means it is always
case-sensitive on Unicode systems).

If you are using GNU Emacs≥25, what locale are you using? FI_fi and most
of the other western locales are based on ISO-14651, so you should
always get case-*in*sensitive orderings, which is what I get with Emacs
26.1. So, evaluating the following should all yield «t»:

(string-collate-lessp "a" "x" "de_DE.utf-8" nil)
(string-collate-lessp "a" "X" "de_DE.utf-8" t)
(string-collate-lessp "a" "x" "fi_FI.utf-8" nil)
(string-collate-lessp "a" "X" "fi_FI.utf-8" t)

Kind regards,

Sebastian

-- 
Insane cobra split the wood
Trader of the lowland breed
Call a jittney, drive away
In the slipstream we will stay



Re: [O] Bug: Table does not align properly [9.1.13 (9.1.13-elpaplus @ /home/diogo/.emacs.d/elpa/org-plus-contrib-20180521/)]

2018-07-14 Thread Nicolas Goaziou
Diogo Ferrari  writes:

> from github, The version there is 9.13.1 and the problem remains

We don't use Github. You can find development version here: 
https://code.orgmode.org/bzg/org-mode




Re: [O] Bug: Table does not align properly [9.1.13 (9.1.13-elpaplus @ /home/diogo/.emacs.d/elpa/org-plus-contrib-20180521/)]

2018-07-14 Thread Diogo Ferrari
from github, The version there is 9.13.1 and the problem remains
On Sat, Jul 14, 2018 at 3:13 AM Nicolas Goaziou 
wrote:

> Hello,
>
> Diogo Ferrari  writes:
>
> > Can I clone that version?
>
> What do you mean?
>
> Regards,
>
> --
> Nicolas Goaziou0x80A93738
>


Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-14 Thread Nicolas Goaziou
Hello,

Heikki Lehvaslaiho  writes:

> I can not see any change in function with the new code. Alphabetical
> sorting is fixedly case sensitive.
>
> I am definitely running the new code for org-table-sort-lines at the head
> of the master branch. I can see there have been changes. Universal argument
> does not change the behaviour, either.

OK. I'm Cc'ing Sebastian, who fixed table sorting recently.

Regards,

-- 
Nicolas Goaziou0x80A93738



Re: [O] Bug: Table does not align properly [9.1.13 (9.1.13-elpaplus @ /home/diogo/.emacs.d/elpa/org-plus-contrib-20180521/)]

2018-07-14 Thread Nicolas Goaziou
Hello,

Diogo Ferrari  writes:

> Can I clone that version?

What do you mean?

Regards,

-- 
Nicolas Goaziou0x80A93738



Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-12 Thread Heikki Lehvaslaiho
I can not see any change in function with the new code. Alphabetical
sorting is fixedly case sensitive.

I am definitely running the new code for org-table-sort-lines at the head
of the master branch. I can see there have been changes. Universal argument
does not change the behaviour, either.

I am running this OS X High Sierra with English as a default language, so
the problem should not be the locale.


 -Heikki

Heikki Lehväslaiho - skype:heikki_lehvaslaiho cell: +358 40 850 6640
http://about.me/heikki

On 4 July 2018 at 19:16, Nicolas Goaziou  wrote:

> Hello,
>
> Heikki Lehvaslaiho  writes:
>
> > org-sort has an optional argument with-case. By default its sorting
> ignores
> > the case. When org-sort is called within a table, it calls
> > org-table-sort-line with the argument. org-table-sort-line defines a let
> > variable sort-fold-case (not with-case) but fails to use either variable
> > when sorting and always sorts with case.
>
> IIRC, it was fixed in master branch. Could you test it?
>
> Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
>


Re: [O] Bug: Table does not align properly [9.1.13 (9.1.13-elpaplus @ /home/diogo/.emacs.d/elpa/org-plus-contrib-20180521/)]

2018-07-11 Thread Diogo Ferrari
Can I clone that version?

On Thu, Jun 7, 2018 at 2:49 PM Nicolas Goaziou 
wrote:

> Diogo Ferrari  writes:
>
> > Would you know when the 9.2 is planned to be released?
>
> Very soon, or so I think. Bastien may have a definitive answer on the
> subject.
>
> Regards,
>


-- 
Diogo Ferrari
PhD Candidate
University of Michigan, Ann Arbor
Department of Political Science
E-mail: dferr...@umich.edu
Website: http://dioferrari.wordpress.com/

Open Source! Use R! Use Linux! Use Emacs! Use Python!

"A vida é a arte de tirar conclusões suficientes de dados insuficientes"


Re: [O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]

2018-07-11 Thread Nick Dokos
Nicolas Goaziou  writes:

> Hello,
>
> Joao Pedro Pedroso  writes:
>
>> This bug seems to be related to the presence
>> of TAB characters in the table.
>
> Could you try master branch (yet to be release Org 9.2), as it may have
> been fixed already.
>
> If it isn't fixed, could you provide an ECM?
>

The SE post says that whatever was broken was fixed in 9.1.6, but you still see 
it
in 9.1.9?

FWIW, I cannot reproduce it in Org mode version 9.1.13 
(release_9.1.13-880-g120f87)


ECM = exemple complet minimal = minimal complete example (aka MWE = minimal 
working example).

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler




Re: [O] Bug: problem with org-agenda and categories [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]

2018-07-11 Thread Nick Dokos
PSA:

This was discussed on the list and the outcome was that it is not a bug.
The OP misused the CATEGORY keyword in a way that has been deprecated since 
2008.
Here's a version of the OP's file that behaves as expected.

More details about the CATEGORY changes and the deprecation can be found at

https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS#L1642

N.B. There are CATEGORY properties under each heading (and since
property drawers are only recognized immediately after a heading
(modulo scheduling information), the new headings are mandatory:

--8<---cut here---start->8---
* the world cup on my agenda

** group stage
:PROPERTIES:
:CATEGORY: groups
:END:
%%(diary-block 6 22 2018 6 22 2018) 7:00 wc: brazil - costa rica (sans 
petersburgo){GE2}
%%(diary-block 6 22 2018 6 22 2018) 10:00 wc: nigeria - islanda 
(volgogrado){GD2}
%%(diary-block 6 22 2018 6 22 2018) 13:00 wc: serbia - suiza (kaliningrado){GE2}
%%(diary-block 6 23 2018 6 23 2018) 07:00 wc: belgica - tunez (otkrytiye, 
moscu){GG2}
%%(diary-block 6 23 2018 6 23 2018) 10:00 wc: mexico - korea (rostov){GF2}
%%(diary-block 6 23 2018 6 23 2018) 13:00 wc: alemania - suecia (sochi){GF2}
%%(diary-block 6 24 2018 6 24 2018) 07:00 wc: inglaterra - panama (nizhny){GG2}
%%(diary-block 6 24 2018 6 24 2018) 10:00 wc: japon - senegal 
(ekaterimburgo){GH2}
%%(diary-block 6 24 2018 6 24 2018) 13:00 wc: colombia - polonia (kazán){GH2}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: uruguay - rusia (samara){GA3}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: egipto - arabia (volgogrado){GA3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: portugal - iran (saransk){GB3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: espanha - marruecos 
(kaliningrado){GB3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: Dinamarca - francia (luzhniki, 
moscu){GC3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: PERÙ - australia (sochi){GC3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: argentina - nigeria (san 
petersburgo){GD3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: croacia - islandia (rostov){GD3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: corea - alemania (kazán){GF3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: mexico - suecia 
(ekaterimburgo){GF3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: brazil - serbia (otkrytiye, 
moscu){GE3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: suiza - costa rica  (nizhny){GE3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: polonia - japon (volgogrado){GH3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: colombia - senegal (samara){GH3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: inglaterra - belgica 
(kaliningrado){GG3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: panama - tunez (saransk){GG3}

** 16
:PROPERTIES:
:CATEGORY: 8
:END:
%%(diary-block 6 30 2018 6 30 2018) 09:00 wc: 1cFrancia - 2dArgentina 
(kazán){16}
%%(diary-block 6 30 2018 6 30 2018) 13:00 wc: 1aUruguay -2bPortugal (sochi){16}
%%(diary-block 7 01 2018 7 01 2018) 09:00 wc: 2aRusia - 1bEspaña (moscu){16}
%%(diary-block 7 01 2018 7 01 2018) 13:00 wc: 2cDinamarca - 1dCroacia 
(nizhny){16}
%%(diary-block 7 02 2018 7 02 2018) 09:00 wc: 1eBrazil - 2fMexico (samara){16}
%%(diary-block 7 02 2018 7 02 2018) 13:00 wc: 1gBelgica - 2hJapon (rostov){16}
%%(diary-block 7 03 2018 7 03 2018) 09:00 wc: 2eSuiza - 1fSuecia (san 
petersburgo){16}
%%(diary-block 7 03 2018 7 03 2018) 13:00 wc: 2gInglaterra - 1hColombia 
(moscu){16}

** 8
:PROPERTIES:
:CATEGORY: 4
:END:
%%(diary-block 7 06 2018 7 06 2018) 09:00 wc: 1qfFrancia - 2qfUruguay 
(nizhny){4}
%%(diary-block 7 06 2018 7 06 2018) 13:00 wc: 5qfBrasil - 6qfBelgica (kazán){4}
%%(diary-block 7 07 2018 7 07 2018) 09:00 wc: 7qfRusia - 8qfCrocia (samara){4}
%%(diary-block 7 07 2018 7 07 2018) 13:00 wc: 3qfSuecia - 4qfInglaterra 
(sochi){4}

** Semifinal
:PROPERTIES:
:CATEGORY: semi-final
:END:
%%(diary-block 7 10 2018 7 10 2018) 09:00 wc: 1sf - 2sf (san petersburgo){SF}
%%(diary-block 7 11 2018 7 11 2018) 09:00 wc: 3sf - 4sf (moscu){SF}

** Final
:PROPERTIES:
:CATEGORY: final
:END:
%%(diary-block 7 14 2018 7 14 2018) 09:00 wc: 1p - 2p (san petersburgo){F}
%%(diary-block 7 15 2018 7 15 2018) 09:00 wc: 1f - 2f (luzhniki, moscu){F}
--8<---cut here---end--->8---

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler




Re: [O] Bug: org-git-link to use SHA1 instead of master@{date} [9.1.13 (9.1.13-elpaplus @ /home/kvaneesh/.emacs.d/elpa/develop/org-plus-contrib-20180702/)]

2018-07-11 Thread Nick Dokos
aneesh.ku...@linux.vnet.ibm.com (Aneesh Kumar K.V) writes:

> So my old org file when following git links is giving me error like
>
> "Log for master only goes back to 'x' date". Can we not refer a link
> via git:/filename::sha1:: ?
>
AFAIK, there is no support for git links in Org mode. Perhaps you have
installed an extension? There is an org-git-link.el in contrib/. Is
that perhaps what you are using? If so, it might have bit-rotted a bit
and might need some TLC to bring it up to snuff (the contrib/ stuff is
just that: it's not part of Org mode proper, although the fact that
the code is immediately available often - but *NOT* always - means
that somebody will take a look and patch it.)

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler




Re: [O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]

2018-07-11 Thread Nicolas Goaziou
Hello,

Joao Pedro Pedroso  writes:

> This bug seems to be related to the presence
> of TAB characters in the table.

Could you try master branch (yet to be release Org 9.2), as it may have
been fixed already.

If it isn't fixed, could you provide an ECM?

Thank you.

Regards,

-- 
Nicolas Goaziou



[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-11 Thread andrés ramírez
Hi Nicolas.
> > I still think this is a bug. Let me explain You why.
> 
> If you try "M-x org-lint" on your document, you'll discover what is your
> problem. In short, your usage of CATEGORY keyword is not possible
> anymore. It's a global keyword, like any other keyword.

I have tried org-lint it suggest me to use :CATEGORY: property. As I
have done on my example. But still It Does not work.

> Use headlines to separate your documents into parts with different
> categories.
I have created also headlines. But even with that. I can not get
previous behaviour.

see my modified file:
--8<---cut here---start->8---
* the world cup on my agenda
** groups
:CATEGORY: 0.6groups
%%(diary-block 6 22 2018 6 22 2018) 7:00 wc: brazil - costa rica (sans 
petersburgo){GE2}
%%(diary-block 6 22 2018 6 22 2018) 10:00 wc: nigeria - islanda 
(volgogrado){GD2}
%%(diary-block 6 22 2018 6 22 2018) 13:00 wc: serbia - suiza (kaliningrado){GE2}
%%(diary-block 6 23 2018 6 23 2018) 07:00 wc: belgica - tunez (otkrytiye, 
moscu){GG2}
%%(diary-block 6 23 2018 6 23 2018) 10:00 wc: mexico - korea (rostov){GF2}
%%(diary-block 6 23 2018 6 23 2018) 13:00 wc: alemania - suecia (sochi){GF2}
%%(diary-block 6 24 2018 6 24 2018) 07:00 wc: inglaterra - panama (nizhny){GG2}
%%(diary-block 6 24 2018 6 24 2018) 10:00 wc: japon - senegal 
(ekaterimburgo){GH2}
%%(diary-block 6 24 2018 6 24 2018) 13:00 wc: colombia - polonia (kazán){GH2}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: uruguay - rusia (samara){GA3}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: egipto - arabia (volgogrado){GA3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: portugal - iran (saransk){GB3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: espanha - marruecos 
(kaliningrado){GB3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: Dinamarca - francia (luzhniki, 
moscu){GC3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: PERÙ - australia (sochi){GC3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: argentina - nigeria (san 
petersburgo){GD3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: croacia - islandia (rostov){GD3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: corea - alemania (kazán){GF3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: mexico - suecia 
(ekaterimburgo){GF3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: brazil - serbia (otkrytiye, 
moscu){GE3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: suiza - costa rica  (nizhny){GE3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: polonia - japon (volgogrado){GH3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: colombia - senegal (samara){GH3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: inglaterra - belgica 
(kaliningrado){GG3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: panama - tunez (saransk){GG3}

** dieciseis
:CATEGORY: hello
%%(diary-block 6 30 2018 6 30 2018) 09:00 wc: 1cFrancia - 2dArgentina 
(kazán){16}
%%(diary-block 6 30 2018 6 30 2018) 13:00 wc: 1aUruguay -2bPortugal (sochi){16}
%%(diary-block 7 01 2018 7 01 2018) 09:00 wc: 2aRusia - 1bEspaña (moscu){16}
%%(diary-block 7 01 2018 7 01 2018) 13:00 wc: 2cDinamarca - 1dCroacia 
(nizhny){16}
%%(diary-block 7 02 2018 7 02 2018) 09:00 wc: 1eBrazil - 2fMexico (samara){16}
%%(diary-block 7 02 2018 7 02 2018) 13:00 wc: 1gBelgica - 2hJapon (rostov){16}
%%(diary-block 7 03 2018 7 03 2018) 09:00 wc: 2eSuiza - 1fSuecia (san 
petersburgo){16}
%%(diary-block 7 03 2018 7 03 2018) 13:00 wc: 2gInglaterra - 1hColombia 
(moscu){16}

** octavos
:CATEGORY: 0.octavos
%%(diary-block 7 06 2018 7 06 2018) 09:00 wc: 1qfFrancia - 2qfUruguay 
(nizhny){4}
%%(diary-block 7 06 2018 7 06 2018) 13:00 wc: 5qfBrasil - 6qfBelgica (kazán){4}
%%(diary-block 7 07 2018 7 07 2018) 09:00 wc: 7qfRusia - 8qfCrocia (samara){4}
%%(diary-block 7 07 2018 7 07 2018) 13:00 wc: 3qfSuecia - 4qfInglaterra 
(sochi){4}
** semifinales
:CATEGORY: 0.6semifi
%%(diary-block 7 10 2018 7 10 2018) 09:00 wc: 1sf - 2sf (san petersburgo){SF}
%%(diary-block 7 11 2018 7 11 2018) 09:00 wc: 3sf - 4sf (moscu){SF}
** la final
:CATEGORY: 0.6final
%%(diary-block 7 14 2018 7 14 2018) 09:00 wc: 1p - 2p (san petersburgo){F}
%%(diary-block 7 15 2018 7 15 2018) 09:00 wc: 1f - 2f (luzhniki, moscu){F}
--8<---cut here---end--->8---

the output(incorrect) is:
--8<---cut here---start->8---
Week-agenda (W28):
Monday  9 July 2018 W28
  Diary:  Martyrdom of the Báb
Tuesday10 July 2018
  jl-diary.agendatest: 9:00.. wc: 1sf - 2sf (san petersburgo){SF}
Wednesday  11 July 2018
  jl-diary.agendatest: 9:00.. wc: 3sf - 4sf (moscu){SF}
Thursday   12 July 2018
Friday 13 July 2018
Saturday   14 July 2018
  jl-diary.agendatest: 9:00.. wc: 1p - 2p (san petersburgo){F}
Sunday 15 July 2018
  jl-diary.agendatest: 9:00.. wc: 1f - 2f (luzhniki, moscu){F}
--8<---cut here---end--->8---

Regards





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-11 Thread rrandr...@gmail.com
Hi Nicolas.

I still think this is a bug. Let me explain You why.
On my shared on this thread agenda file(jl_diary.agendatest.org).
There are several categories on the items for being showed on the
org-agenda. But org-mode chooses the last (among the categories) for
showing on the agenda. In my opinion if something is bad my my agenda
file (jl_diary.agendatest.org). It should be signaled when loading the
agenda, as the org-agenda does when something is wrong with my agenda
files, like  the one I have shared (jl_diary.agendatest.org).

>> I share my agenda among several devices with different emacs versions
>> ("23.4" "25.1" "26.1|26.2|master")
>
> Note that recent Org, i.e., Org 9.0+ do not support Emacs 23 anymore.
I just use the org bundled with emacs with every of this versions. And
everything was smooth just until 26.1

Regards





Re: [O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]

2018-07-11 Thread Joao Pedro Pedroso
This bug seems to be related to the presence
of TAB characters in the table.

Thanks,

J.P.Pedroso



[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-11 Thread andrés ramírez
Hi Nicolas.

> It doesn't look like a bug. The OP may have missed
> `org-agenda-time-grid' variable.

¿What is OP?.
If I do the same on emacs 25.1 I get the expected behaviour. So
something has changed between 25.1 and 26.1. ¿What is the change needed?
for having the same result on both emacs versions 25.1 and 26.1.

Regards





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-11 Thread andrés ramírez
Hi Nicolas.
> > ¿What is OP?.
> 
> Original poster: you.

Thanks for the explanation.

> Emacs 25.1 and 26.1 do not ship the same Org. `org-agenda-time-grid'
> changed between the two releases. You may want to double-check this
> variable.

on 25.1
--8<---cut here---start->8---
This is a list of three items
--8<---cut here---end--->8---

On 26.1
--8<---cut here---start->8---
This is a list of four items
--8<---cut here---end--->8---

It is possible for me to have the previous behaviour. on 26.1
¿What change should i do?.
- on the var
- or on the data

I share my agenda among several devices with different emacs versions
("23.4" "25.1" "26.1|26.2|master")

Regards






[O] bug#32068: obsolescense of #+CATEGORY on org-mode 9.x

2018-07-11 Thread andrés ramírez
Hi Nicolas.
> > ¿What would have been the way a user should discover this incompatibility
> > or obsolescense of the "#+CATEGORY"?.
> 
> I would suggest that user to read the releases notes, located in
> ORG-NEWS files, in particular the "Incompatible changes" sections.
> 
> This particular change was announced in Org 8.3.
> 
> Also, this feature (multiple CATEGORY keywords) was strongly deprecated,
> as pointed out in the old manual, since Org 5.14 (2008).

I see. Something is missing on that comment "Use org-lint for a hint
about how to modify your agenda file".

/usr/share/emacs/26.1/etc/ORG-NEWS

emacs 25.1 has org-version 8.2.10

Debian still have 24.5 as default emacs on debian strech. So this issue
is going to arise again in the future. So just for the notice of future
users.

this:
--8<---cut here---start->8---
#+CATEGORY: world cup
--8<---cut here---end--->8---

should be changed to:
--8<---cut here---start->8---
** world cup (not showed on agenda view)
:PROPERTIES:
:CATEGORY: world cup
:END:
--8<---cut here---end--->8---

Regards





[O] bug#32068: obsolescense of #+CATEGORY on org-mode 9.x (was: bug#32068: 26.1; problem with org-agenda and categories)

2018-07-11 Thread andrés ramírez
Hi Nicolas.
> The correct syntax is
> 
> ** groups
> :PROPERTIES:
> :CATEGORY: 0.6groups
> :END:

it worked. It also worked on emacs 23.4 with org-mode-version 6.33x

> See (info "(org) Property Syntax")

Thanks. For your help on solving this incompatibility.

I would like to add a word here "discoverability".

¿What would have been the way a user should discover this incompatibility
or obsolescense of the "#+CATEGORY"?.

Actually I have seen this behaviour
for more than two months time. because sometimes I use master. So this 
behaviour has
more than two months or merged. But I think this could lead to an
opportunity for explaning how a user should react to this change. On my
case It have not been easy to find the right way of solving this.

Regards





[O] Bug: problem with org-agenda and categories [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]

2018-07-11 Thread rrandresf


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


When evaluating the snippet below:
--8<---cut here---start->8---
(eval-after-load "org"
  '(progn
 overwrite some settings
 (setq org-startup-folded nil ;unfolded
   org-agenda-show-all-dates t
   org-confirm-elisp-link-function nil ;; 4 the scratch call
   org-agenda-include-diary t
   org-agenda-include-all-todo t
   )
 (when (file-directory-p "~/docs/org/deft/")
   (setq org-agenda-files (directory-files "~/docs/org/deft/" t 
".*agendatest\.org$"))
   )
 (define-key org-mode-map (kbd "M-a") nil)
 ))

(require 'org)

(funcall 'org-agenda-list)
--8<---cut here---end--->8---

I am getting (which is not fine):
--8<---cut here---start->8---
Week-agenda (W27):
Monday  2 July 2018 W27
  final:   9:00.. wc: 1eBrazil - 2fMexico (samara){16}
  final:  13:00.. wc: 1gBelgica - 2hJapon (rostov){16}
Tuesday 3 July 2018
  final:   9:00.. wc: 2eSuiza - 1fSuecia (san petersburgo){16}
  final:  13:00.. wc: 2gInglaterra - 1hColombia (moscu){16}
Wednesday   4 July 2018
  Diary:  Independence Day
Thursday5 July 2018
Friday  6 July 2018
   0:38.. now - - - - - - - - - - - - - - - - - - - - - - - - -
   8:00.. 
  final:   9:00.. wc: 1qfFrancia - 2qfUruguay (nizhny){4}
  10:00.. 
  12:00.. 
  final:  13:00.. wc: 5qfBrasil - 6qfBelgica (kazán){4}
  14:00.. 
  16:00.. 
  18:00.. 
  20:00.. 
Saturday7 July 2018
  final:   9:00.. wc: 7qfRusia - 8qfCrocia (samara){4}
  final:  13:00.. wc: 3qfSuecia - 4qfInglaterra (sochi){4}
Sunday  8 July 2018
--8<---cut here---end--->8---

the output should be:
--8<---cut here---start->8---
Week-agenda (W27):
Monday  2 July 2018 W27
  8:   9:00.. wc: 1eBrazil - 2fMexico (samara){16}
  8:  13:00.. wc: 1gBelgica - 2hJapon (rostov){16}
Tuesday 3 July 2018
  8:   9:00.. wc: 2eSuiza - 1fSuecia (san petersburgo){16}
  8:  13:00.. wc: 2gInglaterra - 1hColombia (moscu){16}
Wednesday   4 July 2018
  Diary:  Independence Day
Thursday5 July 2018
Friday  6 July 2018
  4:   9:00.. wc: 1qfFrancia - 2qfUruguay (nizhny){4}
  4:  13:00.. wc: 5qfBrasil - 6qfBelgica (kazán){4}
Saturday7 July 2018
  4:   9:00.. wc: 7qfRusia - 8qfCrocia (samara){4}
  4:  13:00.. wc: 3qfSuecia - 4qfInglaterra (sochi){4}
Sunday  8 July 2018
--8<---cut here---end--->8---

the file ~/docs/org/deft/jl-diary.agendatest.org:
--8<---cut here---start->8---
* the world cup on my agenda
#+CATEGORY: groups
%%(diary-block 6 22 2018 6 22 2018) 7:00 wc: brazil - costa rica (sans 
petersburgo){GE2}
%%(diary-block 6 22 2018 6 22 2018) 10:00 wc: nigeria - islanda 
(volgogrado){GD2}
%%(diary-block 6 22 2018 6 22 2018) 13:00 wc: serbia - suiza (kaliningrado){GE2}
%%(diary-block 6 23 2018 6 23 2018) 07:00 wc: belgica - tunez (otkrytiye, 
moscu){GG2}
%%(diary-block 6 23 2018 6 23 2018) 10:00 wc: mexico - korea (rostov){GF2}
%%(diary-block 6 23 2018 6 23 2018) 13:00 wc: alemania - suecia (sochi){GF2}
%%(diary-block 6 24 2018 6 24 2018) 07:00 wc: inglaterra - panama (nizhny){GG2}
%%(diary-block 6 24 2018 6 24 2018) 10:00 wc: japon - senegal 
(ekaterimburgo){GH2}
%%(diary-block 6 24 2018 6 24 2018) 13:00 wc: colombia - polonia (kazán){GH2}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: uruguay - rusia (samara){GA3}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: egipto - arabia (volgogrado){GA3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: portugal - iran (saransk){GB3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: espanha - marruecos 
(kaliningrado){GB3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: Dinamarca - francia (luzhniki, 
moscu){GC3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: PERÙ - australia (sochi){GC3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: argentina - nigeria (san 
petersburgo){GD3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: croacia - islandia (rostov){GD3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: corea - alemania (kazán){GF3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: mexico - suecia 
(ekaterimburgo){GF3}
%%(diary-block 6 27 2018 6 27 

[O] Bug: org-git-link to use SHA1 instead of master@{date} [9.1.13 (9.1.13-elpaplus @ /home/kvaneesh/.emacs.d/elpa/develop/org-plus-contrib-20180702/)]

2018-07-11 Thread Aneesh Kumar K.V


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


So my old org file when following git links is giving me error like

"Log for master only goes back to 'x' date". Can we not refer a link
via git:/filename::sha1:: ?


Emacs  : GNU Emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.22.30)
 of 2018-06-26
Package: Org mode version 9.1.13 (9.1.13-elpaplus @ 
/home/kvaneesh/.emacs.d/elpa/develop/org-plus-contrib-20180702/)




[O] Bug: Tables not aligning properly [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)]

2018-07-11 Thread Joao Pedro Pedroso


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


Since some versions ago, org-mode stopped aligning tables properly.
This has been commented in StackExchange:
  
https://emacs.stackexchange.com/questions/37828/org-mode-doesnt-align-column-bars-properly

Sincerely,

João Pedro Pedroso

--

Emacs  : GNU Emacs 26.1 (build 1, x86_64-apple-darwin17.6.0, Carbon Version 158 
AppKit 1561.4)
 of 2018-06-11
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ 
/Applications/MacPorts/EmacsMac.app/Contents/Resources/lisp/org/)

current state:
==
(setq
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-timer-default-timer 25
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-agenda-files '("~/private/GTD/work.org" "~/private/GTD/gtd.org" 
"~/private/GTD/home.org")
 org-modules '(org-timer org-w3m org-bbdb org-bibtex org-docview org-gnus 
org-info org-irc org-mhe org-rmail)
 org-mode-hook '((lambda nil (flyspell-mode) (visual-line-mode))
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-show-block-all append local] 5]
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-babel-show-result-all append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
 org-babel-pre-tangle-hook '(save-buffer)
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-log-done t
 org-occur-hook '(org-first-headline-recenter)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers 
org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-support-shift-select 'always
 org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
 org-replace-disputed-keys t
 org-return-follows-link t
 org-clock-in-hook '((lambda nil (if (not org-timer-current-timer) 
(org-timer-set-timer (quote (16))
 org-confirm-shell-link-function 'yes-or-no-p
 org-link-parameters '(("id" :follow org-id-open) ("rmail" :follow 
org-rmail-open :store org-rmail-store-link)
   ("mhe" :follow org-mhe-open :store org-mhe-store-link)
   ("irc" :follow org-irc-visit :store org-irc-store-link)
   ("info" :follow org-info-open :export org-info-export 
:store org-info-store-link)
   ("gnus" :follow org-gnus-open :store org-gnus-store-link)
   ("docview" :follow org-docview-open :export 
org-docview-export :store org-docview-store-link)
   ("bibtex" :follow org-bibtex-open :store 
org-bibtex-store-link)
   ("bbdb" :follow org-bbdb-open :export org-bbdb-export 
:complete org-bbdb-complete-link :store
org-bbdb-store-link)
   ("w3m" :store org-w3m-store-link) ("file+sys") 
("file+emacs") ("doi" :follow org--open-doi-link)
   ("elisp" :follow org--open-elisp-link) ("file" :complete 
org-file-complete-link)
   ("ftp" :follow (lambda (path) (browse-url (concat "ftp:" 
path ("help" :follow org--open-help-link)
   ("http" :follow (lambda (path) (browse-url (concat 
"http:" path
   ("https" :follow (lambda (path) (browse-url (concat 
"https:" path
   ("mailto" :follow (lambda (path) (browse-url (concat 
"mailto:; path
   ("news" :follow (lambda (path) (browse-url (concat 
"news:; path
   ("shell" :follow org--open-shell-link))
 org-image-actual-width '(400)
 org-agenda-custom-commands '(("w" todo "WAITING" nil) ("n" todo "NEXT" nil)
  ("d" "Agenda + Next Actions" ((agenda) (todo 
"NEXT"
 org-directory "~/private/ORG"
 org-default-notes-file "~/private/ORG/notes.org"
 org-list-allow-alphabetical t
 )



[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-11 Thread andrés ramírez
Hi Eli.
> > I am getting (which is not fine):
> 
> Did you report this to the Org developers?  If so, and if they said
> this is a core Emacs bug, could you please point us to the relevant
> discussions with Org developers?

I have just done with org-submit-bug-report

Thanks





[O] bug#32068: obsolescense of #+CATEGORY on org-mode 9.x

2018-07-09 Thread Nicolas Goaziou
Hello,

andrés ramírez  writes:

> ¿What would have been the way a user should discover this incompatibility
> or obsolescense of the "#+CATEGORY"?.

I would suggest that user to read the releases notes, located in
ORG-NEWS files, in particular the "Incompatible changes" sections.

This particular change was announced in Org 8.3.

Also, this feature (multiple CATEGORY keywords) was strongly deprecated,
as pointed out in the old manual, since Org 5.14 (2008).

Regards,

-- 
Nicolas Goaziou0x80A93738





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-09 Thread Nicolas Goaziou
Hello,

andrés ramírez  writes:

> I have tried org-lint it suggest me to use :CATEGORY: property. As I
> have done on my example. But still It Does not work.

> * the world cup on my agenda
> ** groups
> :CATEGORY: 0.6groups

The correct syntax is

** groups
:PROPERTIES:
:CATEGORY: 0.6groups
:END:

See (info "(org) Property Syntax")

Regards,

-- 
Nicolas Goaziou0x80A93738





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-08 Thread Nicolas Goaziou
Hello,

"rrandr...@gmail.com"  writes:

> I still think this is a bug. Let me explain You why.
> On my shared on this thread agenda file(jl_diary.agendatest.org).
> There are several categories on the items for being showed on the
> org-agenda. But org-mode chooses the last (among the categories) for
> showing on the agenda. In my opinion if something is bad my my agenda
> file (jl_diary.agendatest.org). It should be signaled when loading the
> agenda, as the org-agenda does when something is wrong with my agenda
> files, like  the one I have shared (jl_diary.agendatest.org).

If you try "M-x org-lint" on your document, you'll discover what is your
problem. In short, your usage of CATEGORY keyword is not possible
anymore. It's a global keyword, like any other keyword.

Use headlines to separate your documents into parts with different
categories.

Regards,

-- 
Nicolas Goaziou0x80A93738





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-07 Thread Nicolas Goaziou
Hello,

andrés ramírez  writes:

> It is possible for me to have the previous behaviour. on 26.1
> ¿What change should i do?.

You can definitely get the previous behaviour, but I cannot remember the
change. Just look at the docstring, it is probably straightforward.

> I share my agenda among several devices with different emacs versions
> ("23.4" "25.1" "26.1|26.2|master")

Note that recent Org, i.e., Org 9.0+ do not support Emacs 23 anymore.

Regards,

-- 
Nicolas Goaziou0x80A93738





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-07 Thread Nicolas Goaziou
Hello,

andrés ramírez  writes:

>> It doesn't look like a bug. The OP may have missed
>> `org-agenda-time-grid' variable.
>
> ¿What is OP?.

Original poster: you.

> If I do the same on emacs 25.1 I get the expected behaviour. So
> something has changed between 25.1 and 26.1. ¿What is the change needed?
> for having the same result on both emacs versions 25.1 and 26.1.

Emacs 25.1 and 26.1 do not ship the same Org. `org-agenda-time-grid'
changed between the two releases. You may want to double-check this
variable.

Regards,

-- 
Nicolas Goaziou0x80A93738





[O] bug#27140: Different key bindings between GUI emacs and terminal emacs

2018-07-07 Thread Jean-Christophe Helary
Sorry, I missed that. Proceed with closing and if there is an issue I'll send a 
report again.

Jean-Christophe 

> On Jul 7, 2018, at 20:12, Nicolas Goaziou  wrote:
> 
> Nicolas Goaziou  writes:
> 
>> I think I fixed it in Org's master branch (aka Org 9.2).
>> 
>> Meanwhile, I think setting `org-use-extra-keys' to a non-nil value
>> should do the trick.
>> 
>> Could you confirm it?
> 
> I'm closing this report. Since there was no answer from the OP, I assume
> the issue is fixed.





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-07 Thread Eli Zaretskii
> From: Nicolas Goaziou 
> Cc: rrandr...@gmail.com,  32...@debbugs.gnu.org
> Date: Sat, 07 Jul 2018 13:05:53 +0200
> 
> It doesn't look like a bug. The OP may have missed
> `org-agenda-time-grid' variable.
> 
> I suggest to close this bug, if the OP doesn't object to it.

Thanks.  I will wait a few days and close it if no objections are
posted.





[O] bug#26467: 25.2; [Org mode] Call dot babel from elisp generate invalid image

2018-07-07 Thread Nicolas Goaziou
Nicolas Goaziou  writes:

> I can achieve the desired effect with:
>
> #+name: nodes
> | From | To | Weight |
> |--++|
> | A| B  |  3 |
> | A| C  |  2 |
> | B| D  |  4 |
> | B| E  |  5 |
> | C| F  | 10 |
>
> #+begin_src elisp :file /tmp/a.png :var nodes=nodes :results file
> (defun rowfun (x)
>   (format "%s -> %s [label=%s];" (nth 0 x) (nth 1 x) (nth 2 x)))
> (defun dotgen (nodes)
>   (format "digraph {\nnode [shape=circle]\n%s\n}"
>   (mapconcat #'rowfun nodes "\n")))
> (dotgen nodes)
> #+end_src
>
> I don't see why you would need to call `org-babel-execute:dot'.
>
> Does it fix your issue?

Since the OP didn't answer, I assume this is now fixed.

I'm closing this report.





[O] bug#22735: bug#22776: interactive org-set-effort (C-c C-x e) and column view direct index selection do not handle Effort_ALL with more than 10 entries

2018-07-07 Thread Nicolas Goaziou
Nicolas Goaziou  writes:

> I've changed `org-set-effort' to use `completing-read' for allowed
> values instead of relying on position in list. The prefix argument now
> means "increment". 
>
> This is simpler and less exotic.
>
> WDYT?

Since there is no answer from the OP, I assume this is fixed.

I'm closing the bug report.





[O] bug#24595: 24.5; Org manual indexing for #+STARTUP entries

2018-07-07 Thread Nicolas Goaziou
Hello,

Drew Adams  writes:

>> This should be reported to Org developers, not here.
>
> Org is part of distributed Emacs.  Bug reports for it should be
> dispatched from here automatically, or Org maintainers should
> pick them up here.
>
> I don't use Org.  Just reporting the problem, in case it helps.

It does. The new manual (for Org 9.2) hopefully fixes these. Please
open a new bug report if you think it doesn't.

I'm closing this one.

Thank you.

Regards,

-- 
Nicolas Goaziou0x80A93738





[O] bug#27068: 25.2; org-odt-export-to-odt error when filename contains Chinese chars

2018-07-07 Thread Nicolas Goaziou
Nicolas Goaziou  writes:

> I cannot reproduce it. More specifically, I created a file named "童.org",
> added "* Headline" in it and exported it to ODT without problem.
>
> Could you provide a recipe for the issue you are encountering? If you
> are not able to reproduce it anymore, could you tell me so I can close
> this bug?

I'm closing this report since there was no answer from the OP. I assume
the issue is fixed.





[O] bug#27140: Different key bindings between GUI emacs and terminal emacs

2018-07-07 Thread Nicolas Goaziou
Nicolas Goaziou  writes:

> I think I fixed it in Org's master branch (aka Org 9.2).
>
> Meanwhile, I think setting `org-use-extra-keys' to a non-nil value
> should do the trick.
>
> Could you confirm it?

I'm closing this report. Since there was no answer from the OP, I assume
the issue is fixed.





[O] bug#31273: 27.0.50; org: #+begin_right block is not exported correctly

2018-07-07 Thread Nicolas Goaziou
I'm closing this report, which is not considered as a bug.

-- 
Nicolas Goaziou0x80A93738





[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-07 Thread Nicolas Goaziou
Hello,

Eli Zaretskii  writes:

>> When evaluating the snippet below:
>> --8<---cut here---start->8---
>> (eval-after-load "org"
>>   '(progn
>>  overwrite some settings
>>  (setq org-startup-folded nil ;unfolded
>>org-agenda-show-all-dates t
>>org-confirm-elisp-link-function nil ;; 4 the scratch call
>>org-agenda-include-diary t
>>org-agenda-include-all-todo t
>>)
>>  (when (file-directory-p "~/docs/org/deft/")
>>(setq org-agenda-files (directory-files "~/docs/org/deft/" t 
>> ".*agendatest\.org$"))
>>)
>>  (define-key org-mode-map (kbd "M-a") nil)
>>  ))
>> 
>> (require 'org)
>> 
>> (funcall 'org-agenda-list)
>> --8<---cut here---end--->8---
>> 
>> I am getting (which is not fine):
>
> Did you report this to the Org developers?  If so, and if they said
> this is a core Emacs bug, could you please point us to the relevant
> discussions with Org developers?

It doesn't look like a bug. The OP may have missed
`org-agenda-time-grid' variable.

I suggest to close this bug, if the OP doesn't object to it.

Regards,

-- 
Nicolas Goaziou





Re: [O] Bug: duplicated output in inline code block exports

2018-07-07 Thread Nicolas Goaziou
Hello,

"Berry, Charles"  writes:

>> On Jul 5, 2018, at 10:46 AM, William Denton  wrote:
>> 
>> Here's a very simple R command in an inline code block:
>> 
>> # -
>> What is 1 + 1?  src_R{1+1} {{{results(=2=)}}}
>> # -
>> 
>> Exporting this to PDF we get:
>> 
>> # -
>> What is 1 + 1? 2 2
>
> Or exporting to to latex 
>
> What is 1 + 1?  \texttt{2} \texttt{2}
>
> The results macro gets initialized by `org-macro-initialize-templates'
> which is run run before babel, the macro returns `=2=', and babel does
> not remove this when it adds the result again.

Fixed. Thank you.
> Also, shouldn't the docstring for `org-macro-initialize-templates'
> mention that "n", "author", "email", "keyword", "results", and "title"
> get set?

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



[O] bug#32068: 26.1; problem with org-agenda and categories

2018-07-06 Thread Eli Zaretskii
> From: rrandr...@gmail.com
> Date: Fri, 06 Jul 2018 00:46:14 +
> 
> 
> When evaluating the snippet below:
> --8<---cut here---start->8---
> (eval-after-load "org"
>   '(progn
>  overwrite some settings
>  (setq org-startup-folded nil ;unfolded
>org-agenda-show-all-dates t
>org-confirm-elisp-link-function nil ;; 4 the scratch call
>org-agenda-include-diary t
>org-agenda-include-all-todo t
>)
>  (when (file-directory-p "~/docs/org/deft/")
>(setq org-agenda-files (directory-files "~/docs/org/deft/" t 
> ".*agendatest\.org$"))
>)
>  (define-key org-mode-map (kbd "M-a") nil)
>  ))
> 
> (require 'org)
> 
> (funcall 'org-agenda-list)
> --8<---cut here---end--->8---
> 
> I am getting (which is not fine):

Did you report this to the Org developers?  If so, and if they said
this is a core Emacs bug, could you please point us to the relevant
discussions with Org developers?

Thanks.





Re: [O] Bug: duplicated output in inline code block exports

2018-07-05 Thread Berry, Charles



> On Jul 5, 2018, at 10:46 AM, William Denton  wrote:
> 
> Here's a very simple R command in an inline code block:
> 
> # -
> What is 1 + 1?  src_R{1+1} {{{results(=2=)}}}
> # -
> 
> Exporting this to PDF we get:
> 
> # -
> What is 1 + 1? 2 2

Or exporting to to latex 

What is 1 + 1?  \texttt{2} \texttt{2}

The results macro gets initialized by `org-macro-initialize-templates' which is 
run run before babel, the macro returns `=2=', and babel does not remove this 
when it adds the result again.

A work-around is to put this null macro:

# 
#+macro: results
# 

in your buffer to strip out the existing inline results.

I do not get why this wasn't detected before - the pre-babel call to 
{{{results( )}}} has been in the code since last year.

Also, shouldn't the docstring  for `org-macro-initialize-templates' mention 
that "n", "author", "email", "keyword", "results", and "title" get set?

Chuck






[O] Bug: duplicated output in inline code block exports

2018-07-05 Thread William Denton

Here's a very simple R command in an inline code block:

# -
What is 1 + 1?  src_R{1+1} {{{results(=2=)}}}
# -

Exporting this to PDF we get:

# -
What is 1 + 1? 2 2
# -

For some reason the "2" is duplicated.

Same thing with Ruby.  I had a look at recent commits (I recompiled from current 
source) but couldn't see where this might have started.


Bill
--
William Denton :: Toronto, Canada   ---   Listening to Art: 
https://listeningtoart.org/
https://www.miskatonic.org/ ---   GHG.EARTH: http://ghg.earth/
Caveat lector.  ---   STAPLR: http://staplr.org/



Re: [O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-04 Thread Nicolas Goaziou
Hello,

Heikki Lehvaslaiho  writes:

> org-sort has an optional argument with-case. By default its sorting ignores
> the case. When org-sort is called within a table, it calls
> org-table-sort-line with the argument. org-table-sort-line defines a let
> variable sort-fold-case (not with-case) but fails to use either variable
> when sorting and always sorts with case.

IIRC, it was fixed in master branch. Could you test it?

Thank you.

Regards,

-- 
Nicolas Goaziou



[O] bug: org-table-sort-lines does only case sensitive alphabetical sorting

2018-07-03 Thread Heikki Lehvaslaiho
org-sort has an optional argument with-case. By default its sorting ignores
the case. When org-sort is called within a table, it calls
org-table-sort-line with the argument. org-table-sort-line defines a let
variable sort-fold-case (not with-case) but fails to use either variable
when sorting and always sorts with case.

This is with the very latest org:
Org mode version 9.1.13 (9.1.13-elpa @
/Users/helehvas/.emacs.d/elpa/org-20180702/)

 -Heikki

Heikki Lehväslaiho - skype:heikki_lehvaslaiho cell: +358 40 850 6640
http://about.me/heikki


<    4   5   6   7   8   9   10   11   12   13   >