Re: [O] orgalist list item spacing

2018-09-16 Thread Eric S Fraga
On Saturday, 15 Sep 2018 at 11:03, Eric Abrahamsen wrote:
> Eric S Fraga  writes:
>> Long standing "feature" of org.  Unless you do require a blank line
>> between items, it is impossible to differentiate between the start of a
>> numbered item and the continuation of the previous item in this case.
>
> Huh, I've never seen this in org-mode proper. 

Silly me.  I was comparing apples and oranges.  In org mode, I use
visual-line-mode and no filling; in message mode, I use
auto-fill.  Sorry for my intervention!

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-783-g97fac4



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] Move (the children of) a subtree to another subtree programmatically

2018-09-16 Thread Adam Porter
See the SCOPE argument to org-map-entries.  I'd also recommend using
org-refile instead of org-cut/paste-subtree.

You may also find the org-datetree system helpful.




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.