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

[Lambda Coder]

On Sun, Dec 18, 2016 at 3:39 PM, Nicolas Goaziou 
wrote:

> Could you send an updated patch?
>
>
> Regards,
>
> --
> Nicolas Goaziou
>


See attached patch for Exporting chapter against maint. Also my notes to
your comments.

--Lambda Coder.


0002-Editorial-revisions-to-the-manual.patch.gz
Description: GNU Zip compressed data


20161219CommentsFromNicolas.txt.gz
Description: GNU Zip compressed data

[O] [PATCH] Fix org-clock-load

[Matt Lundin]

Since commit fda64f1ae2110175662b52daa3a5ec0f967f0c0d on November 6,
org-clock-load no longer restores clocks in org-clock-persist-file. The
contents of the file look like this:

--8<---cut here---start->8---
(setq org-clock-stored-history '(("/home/matt/org/inbox.org" . 39479) 
("/home/matt/org/reading.org" . 63478)))
--8<---cut here---end--->8---

The files both exist; the position information is correct; and
org-clock-persist is t. And yet after calling org-clock-load,
org-clock-history, org-clock-loaded, and org-clock-stored-history remain
nil.

The problem, it seems, is that the logic/order of the if statement was
reversed in the commit above. The attached patch should fix the issue.

Best,
Matt

>From 6d649016fbbfaa28c902ee1e71c20ecf332f8a14 Mon Sep 17 00:00:00 2001
From: Matt Lundin 
Date: Mon, 19 Dec 2016 17:24:10 -0600
Subject: [PATCH] org-clock: Fix org-clock-load

* lisp/org-clock.el: (org-clock-load): Fix incorrect order in if
statement that was preventing org-load from loading stored data and
populating org-clock-history.
---
 lisp/org-clock.el | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index 65c13fdf2..6e58ce91a 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -2962,9 +2962,9 @@ The details of what will be saved are regulated by the variable
 (defun org-clock-load ()
   "Load clock-related data from disk, maybe resuming a stored clock."
   (when (and org-clock-persist (not org-clock-loaded))
-(if (file-readable-p org-clock-persist-file)
-	(message "Restoring clock data")
-  (message "Not restoring clock data; %S not found" org-clock-persist-file)
+(if (not (file-readable-p org-clock-persist-file))
+	(message "Not restoring clock data; %S not found" org-clock-persist-file)
+  (message "Restoring clock data")
   ;; Load history.
   (load-file org-clock-persist-file)
   (setq org-clock-loaded t)
-- 
2.11.0

Re: [O] Defining macros globally

[Nicolas Goaziou]

Hello,

"Charles C. Berry"  writes:

> On Mon, 19 Dec 2016, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Arun Isaac  writes:
>>
>>> Is it possible to define macros globally, probably in the ~/.emacs init
>>> file with some elisp, instead of on a per-file basis using the #+MACRO
>>> keyword?
>>
>> This is not possible ATM.
>
> Perhaps the OP could do this?
>
> #+BEGIN_SRC emacs-lisp
>(setq my-new-macros
>   '(("def" . "d $1 e $2 f")
> ("ghi" . "GHI only")))
>
>(defun add-my-macros (&rest x)
>  (nconc org-macro-templates my-new-macros))
>
>(advice-add 'org-macro-initialize-templates :filter-return
> #'add-my-macros)
>
>
> #+END_SRC
>
> Admittedly, this invites problems if `my-new-macros' is malformed. But 
> there could be ways to impose a discipline that would assure that it is 
> not.

I added `org-export-global-macros' in master. It's Christmas, after all.

Regards,

-- 
Nicolas Goaziou

Re: [O] [ANN] Substantial changes to sitemap generation

[Nicolas Goaziou]

Hello,

Thibault Marin  writes:

> However, I initially got an error when running =make=, there seems to be
> a typo in l. 14542 of org.texi ("@cod{" should be "@code{"):
> http://orgmode.org/cgit.cgi/org-mode.git/tree/doc/org.texi#n14542

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] [ANN] Substantial changes to sitemap generation

[Thibault Marin]

Nicolas Goaziou writes:

> Hello,
>
> I just pushed a revamp of sitemap generation during publishing process.
> If you tweaked sitemap, you almost certainly need to update your
> settings.
>
> Basically, the changes at the property level are:
>
>   - :sitemap-sans-extension and :sitemap-file-entry-format were removed
>   - :sitemap-function changed its signature
>   - :sitemap-format-entry was added
>
> Also, the patch set implements the following function
>
>   `org-publish-find-property'
>
> See `org-publish-project-alist' for details (or the manual).
>
> Feedback welcome. Ideally, if it is better, we might want to propagate
> the same kind of change to index generation.
>
> Regards,

Hi,

Thanks for pushing the sitemap change, it still works for me (from the
sitemap-wip branch).  I am able to generate a list of posts from the
sitemap and #+INCLUDE it in other pages.

However, I initially got an error when running =make=, there seems to be
a typo in l. 14542 of org.texi ("@cod{" should be "@code{"):
http://orgmode.org/cgit.cgi/org-mode.git/tree/doc/org.texi#n14542

Thanks again.

thibault

Re: [O] issue with deadline and schedule on same line

[Divan Santana]

Nicolas Goaziou  writes:

> Hello,
>
> Divan Santana  writes:
>
>> Hi Org users
>>
>> Quick one. Having an issue when trying to fire up `org-agenda`.
>>
>> It errors with:
>>
>> ```
>> org-agenda-get-day-entries: Wrong type argument: number-or-marker-p, 
>> "<2016-12-20 Tue +1m>"
>
> This was fixed a couple of days ago.

Thanks a lot.

Re: [O] Remove Org from Emacs repository?

[Achim Gratz]

Phillip Lord writes:
> I think there's only a few problems, actually. package.el initialization
> is all or nothing at the moment, and is disabled on emacs -q. Neither of
> these would make sense if we wanted in built packages.

My opinion is that unless package.el adds explicit support for
system-level packetization decisions (i.e. for admins or distributions)
it's not going to gain widespread support from that small, but important
set of folks.  Of course the user will then have to be able to override
these like deactivation of packages, installing different versions, etc.
Before long it also needs to be able to cope with different package
archives simultaneously especially when those have incompatible
numbering schemes.

> It's not strictly necessary, though. The current idea is to not to use
> packages but to, essentially, move the lisp of packages in ELPA into
> place in the build. package.el need not be involved then.

Yes I know.  Which is in essence prolonging the current state of affairs
as far as the users are concerned.  If it gets things moving into the
right direction I'll be glad.  I just had hoped for some more general
(some would say radical) solution.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: [O] ido not working with org9

[Samuel Wales]

ido-hacks works with org 9.  it makes everything use ido, and speeds it up.

i do not know about iswitchb.

Re: [O] Defining macros globally

[Charles C. Berry]

On Mon, 19 Dec 2016, Nicolas Goaziou wrote:


Hello,

Arun Isaac  writes:


Is it possible to define macros globally, probably in the ~/.emacs init
file with some elisp, instead of on a per-file basis using the #+MACRO
keyword?


This is not possible ATM.


Perhaps the OP could do this?

#+BEGIN_SRC emacs-lisp
  (setq my-new-macros
'(("def" . "d $1 e $2 f")
  ("ghi" . "GHI only")))

  (defun add-my-macros (&rest x)
(nconc org-macro-templates my-new-macros))

  (advice-add 'org-macro-initialize-templates :filter-return
  #'add-my-macros)


#+END_SRC

Admittedly, this invites problems if `my-new-macros' is malformed. But 
there could be ways to impose a discipline that would assure that it is 
not.



HTH,

Chuck

Re: [O] Remove Org from Emacs repository?

[Scott Randby]

+1 for Keeping Org in Emacs.

Scott Randby

On 12/18/2016 08:20 AM, Carsten Dominik wrote:
> Dear all,
> 
> I'd hate to see Org removed from Emacs.  It took a lot of work to get it
> in, and I believe that the vast majority of Emacs users does not install
> packages.  For a newbie to get to Emacs and to be able to open a .org
> file is a big plus.  So my vote goes toward keeping it in.
> 
> Carsten
> 
> On Sun, Dec 18, 2016 at 10:22 AM,  > wrote:
> 
> 2 cents from me...
> 
> Besides I continuously see many users praising Emacs just for Org
> presence (they even may be completely non-technical users), I'm
> personally think Org may be removed from Emacs distribution because:
> 
> 1) all Reuben's argument seems sane;
> 2) there are situations when someone wants particular version of Org,
>and it may be not tne one bundled with Emacs. In this case someone
>should perform extra steps to ensure things are going the right way.
>When Org will be available only from ELPA, it will be SPOT for
> such cases.
> 
> Reuben Thomas mailto:r...@sc3d.org>> writes:
> 
> > Now that Emacs has had package.el for some years, and Org is installable
> > directly from GNU ELPA, would it be a good idea to remove Org from 
> Emacs's
> > source repository?
> >
> > The current situation is left over from before Emacs had package.el, 
> and I
> > see no compelling reason to keep it. Org is too big and distinct to be
> > swallowed by Emacs; it doesn't make much sense to keep its current 
> half-in,
> > half-out state; so logically it seems sensible to take it out.
> >
> > I am asking this question from an Org point of view; I will ask the 
> Emacs
> > maintainers separately for their perspective.
> >
> > I think it would benefit Emacs too, as there would be less code to 
> maintain
> > (even though Org is quasi-external at present, it still has to build
> > successfully as part of an Emacs build), and the Emacs distribution 
> would
> > be slimmer for non-Org users.
> >
> > Of course, Emacs "distributions" would still be able to include Org
> > out-of-the box if they wished.
> >
> > --
> > http://rrt.sc3d.org
> 
> 

Re: [O] Defining macros globally

[Kaushal Modi]

On Mon, Dec 19, 2016, 7:12 PM Arun Isaac  wrote:

>
> Is it possible to define macros globally, probably in the ~/.emacs init
> file with some elisp, instead of on a per-file basis using the #+MACRO
> keyword?
>

You can choose to put all macros in a single org file, and then add that
one file as a #+SETUPFILE in all the org files where you wish to use those
macros.

> --

Kaushal Modi

Re: [O] Remove Org from Emacs repository?

[Phillip Lord]

Achim Gratz  writes:
>> Now that package.el is mature, there's no need for Emacs to include all
>> this stuff in its source releases.
>
> That assertion isn't universally accepted as true.  Org in particular
> continues to show how the integration into Emacs as well as some
> functionality in package.el itself is still lacking.  True packetization
> of Emacs' "built-in" packages is further hindered by the fact that
> package.el is currently solely "user-centric" and lacks the usual
> facilities for curating package selection at the installation level.

I think there's only a few problems, actually. package.el initialization
is all or nothing at the moment, and is disabled on emacs -q. Neither of
these would make sense if we wanted in built packages.

It's not strictly necessary, though. The current idea is to not to use
packages but to, essentially, move the lisp of packages in ELPA into
place in the build. package.el need not be involved then.

Phil

[O] [ANN] Substantial changes to sitemap generation

[Nicolas Goaziou]

Hello,

I just pushed a revamp of sitemap generation during publishing process.
If you tweaked sitemap, you almost certainly need to update your
settings.

Basically, the changes at the property level are:

  - :sitemap-sans-extension and :sitemap-file-entry-format were removed
  - :sitemap-function changed its signature
  - :sitemap-format-entry was added

Also, the patch set implements the following function

  `org-publish-find-property'

See `org-publish-project-alist' for details (or the manual).

Feedback welcome. Ideally, if it is better, we might want to propagate
the same kind of change to index generation.

Regards,

-- 
Nicolas Goaziou0x80A93738

Re: [O] Remove Org from Emacs repository?

[Phillip Lord]

Reuben Thomas  writes:

> On 18 December 2016 at 13:20, Carsten Dominik  wrote:
>
>> Dear all,
>>
>> I'd hate to see Org removed from Emacs.  It took a lot of work to get it
>> in, and I believe that the vast majority of Emacs users does not install
>> packages.  For a newbie to get to Emacs and to be able to open a .org file
>> is a big plus.  So my vote goes toward keeping it in.
>>
>
> ​Since you're responsible for org-mode, and I guess you're happy with the
> coordination between (your) upstream and Emacs, then ​I agree it should
> continue to be distributed out of the box.
>
> However, your comments raise a couple of thoughts:
>
> 1. Is there something hard about packages that could be made easier? For
> example, Atom seems to get along fine without many built-in packages, so
> that most users expect to install some.
>
> 2. Is there any possibility to make org-mode a build-time dependency of
> Emacs, like the C libraries that it requires, or is that a silly idea? That
> could permit it to be shipped as built-in, without having its source
> duplicated in Emacs's repository.

This kind of idea is, indeed, being actively considered on
emacs-devel. In fact, I managed to get a simple version of this working
using package.el during the build process. The idea would be that
packages in ELPA format could be made available to Emacs during the
build and then be packaged with the tarball as now.

The general feedback on my implementation was negative, but the general
principle is something that people are keen to pursue, hopefully for
Emacs-26. Org-mode would make a good test case for this.

Another possibility would be to extend the current "autoload"
functionality, so that it can install via package.el before
autoloading. Might work, but not tried that yet.


Phil

Re: [O] Remove Org from Emacs repository?

[Reuben Thomas]

On 19 December 2016 at 15:32, Phillip Lord 
wrote:

>
> This kind of idea is, indeed, being actively considered on
> emacs-devel.


​That's good to hear!​

In fact, I managed to get a simple version of this working
> using package.el during the build process. The idea would be that
> packages in ELPA format could be made available to Emacs during the
> build and then be packaged with the tarball as now.
>

​That would be great, it would certainly do what I'm after.​

-- 
http://rrt.sc3d.org

Re: [O] issue with deadline and schedule on same line

[Nicolas Goaziou]

Hello,

Divan Santana  writes:

> Hi Org users
>
> Quick one. Having an issue when trying to fire up `org-agenda`.
>
> It errors with:
>
> ```
> org-agenda-get-day-entries: Wrong type argument: number-or-marker-p, 
> "<2016-12-20 Tue +1m>"

This was fixed a couple of days ago.

Regards,

-- 
Nicolas Goaziou

Re: [O] Defining macros globally

[Nicolas Goaziou]

Hello,

Arun Isaac  writes:

> Is it possible to define macros globally, probably in the ~/.emacs init
> file with some elisp, instead of on a per-file basis using the #+MACRO
> keyword?

This is not possible ATM.

Regards,

-- 
Nicolas Goaziou

[O] Defining macros globally

[Arun Isaac]

Is it possible to define macros globally, probably in the ~/.emacs init
file with some elisp, instead of on a per-file basis using the #+MACRO
keyword?

Thanks,
Arun Isaac.


signature.asc
Description: PGP signature

[O] issue with deadline and schedule on same line

[Divan Santana]

Hi Org users

Quick one. Having an issue when trying to fire up `org-agenda`.

It errors with:

```
org-agenda-get-day-entries: Wrong type argument: number-or-marker-p, 
"<2016-12-20 Tue +1m>"
```

That's when one tries to read this file in:

```
* Tasks
** TODO [#B] Do budget for next Month - 20th:money:admin:2pomodoros:
DEADLINE: <2016-12-20 Tue +1m> SCHEDULED: <2016-12-20 Tue +1m>

```

Is this expected? Or am I doing something wrong?

If I have just DEADLINE or SCHEDULED entry then `org-agenda` fires up
without an issue.

Any ideas?

 System Info :computer:
- OS: gnu/linux
- Emacs: 25.1.1
- Spacemacs: 0.200.5
- Spacemacs branch: master (rev. 664ba6ab)
- Graphic display: t
- Distribution: spacemacs
- Editing style: vim
- Completion: helm
- Layers:
```elisp
((auto-completion :variables auto-completion-enable-snippets-in-popup t 
auto-completion-private-snippets-directory
  (list "~/.spacemacs.d/snippets" 
"~/.spacemacs.d/private/snippets"))
 better-defaults command-log colors csv dash docker deft
 (elfeed :variables rmh-elfeed-org-files
 (list "~/.spacemacs.d/elfeed.org" 
"~/.spacemacs.d/private/elfeed-private.org")
 elfeed-use-curl t url-queue-timeout 60)
 emacs-lisp erc finance git github html
 (markdown :variables markdown-live-preview-engine 'vmd)
 (mu4e :variables mu4e-installation-path "/usr/share/emacs/site-lisp")
 nginx
 (org :variables org-enable-github-support t)
 pandoc pass pdf-tools php puppet python ranger ruby search-engine
 (shell :variables shell-default-position 'full shell-default-shell 'multi-term)
 shell-scripts slack
 (spell-checking :variables spell-checking-enable-by-default nil)
 sql syntax-checking systemd themes-megapack twitter vagrant windows-scripts 
xkcd yaml)
```
- System configuration features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND 
GPM DBUS GCONF GSETTINGS NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT 
ZLIB TOOLKIT_SCROLL_BARS GTK3 X11

Re: [O] issue with deadline and schedule on same line

[Divan Santana]

> Hi Org users
>
> Quick one. Having an issue when trying to fire up `org-agenda`.
>
> It errors with:
>
> ```
> org-agenda-get-day-entries: Wrong type argument: number-or-marker-p, 
> "<2016-12-20 Tue +1m>"
> ```
>
> That's when one tries to read this file in:
>
> ```
> * Tasks
> ** TODO [#B] Do budget for next Month - 20th:money:admin:2pomodoros:
> DEADLINE: <2016-12-20 Tue +1m> SCHEDULED: <2016-12-20 Tue +1m>
>
> ```
>
> Is this expected? Or am I doing something wrong?
>
> If I have just DEADLINE or SCHEDULED entry then `org-agenda` fires up
> without an issue.
>
> Any ideas?
>
>  System Info :computer:
> - OS: gnu/linux
> - Emacs: 25.1.1
> - Spacemacs: 0.200.5
> - Spacemacs branch: master (rev. 664ba6ab)
> - Graphic display: t
> - Distribution: spacemacs
> - Editing style: vim
> - Completion: helm
> - Layers:
> ```elisp
> ((auto-completion :variables auto-completion-enable-snippets-in-popup t 
> auto-completion-private-snippets-directory
>   (list "~/.spacemacs.d/snippets" 
> "~/.spacemacs.d/private/snippets"))
>  better-defaults command-log colors csv dash docker deft
>  (elfeed :variables rmh-elfeed-org-files
>  (list "~/.spacemacs.d/elfeed.org" 
> "~/.spacemacs.d/private/elfeed-private.org")
>  elfeed-use-curl t url-queue-timeout 60)
>  emacs-lisp erc finance git github html
>  (markdown :variables markdown-live-preview-engine 'vmd)
>  (mu4e :variables mu4e-installation-path "/usr/share/emacs/site-lisp")
>  nginx
>  (org :variables org-enable-github-support t)
>  pandoc pass pdf-tools php puppet python ranger ruby search-engine
>  (shell :variables shell-default-position 'full shell-default-shell 
> 'multi-term)
>  shell-scripts slack
>  (spell-checking :variables spell-checking-enable-by-default nil)
>  sql syntax-checking systemd themes-megapack twitter vagrant windows-scripts 
> xkcd yaml)
> ```
> - System configuration features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND 
> GPM DBUS GCONF GSETTINGS NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF 
> XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11

Didn't include the org version, whoops.

Org mode version 9.0.2 (9.0.2-elpaplus @ 
/home/admin/.emacs.d/elpa/org-plus-contrib-20161214/)

Re: [O] Android org app with sync?

[Ramon Diaz-Uriarte]

Dear Alasdair,


On Sun, 18-12-2016, at 01:59, Alasdair McAndrew  wrote:
> I'm sure this has been asked and answered many times before, but
> I've hunted about - both on the web and on Google Play - to find
> some app which can sync with my org files.  The closest I've come
> is orgzly:
>
> https://play.google.com/store/apps/details?id=com.orgzly
>
> which however only syncs with Dropbox, which I don't use (I use a
> self-hosted ownCloud instead).
>
> Are there any other apps which will allow me to update and edit
> org files on my android device, and have them sync automatically?
>
> I guess I can probably use orgzly with a local file, and have a
> third party app sync with my ownCloud files.  Seems like extra
> fuss, though!


You can used orgzly with syncthing (syncing the directory where file
reading from/writing to takes place) so Dropbox is not needed. I assume
something similar could be done with ownCloud.

That said, at least some of us are still waiting for Orgzly to become free
software: https://plus.google.com/112212983680346701286/posts/hGnkkxDsUjT

But

http://www.orgzly.com/help#Source

doesn't give many specifics.


I use MobileOrg (the app and link Eric gave).


Best,

R.


>
> Thanks,
> Alasdair


--
Ramon Diaz-Uriarte
Department of Biochemistry, Lab B-25
Facultad de Medicina
Universidad Autónoma de Madrid
Arzobispo Morcillo, 4
28029 Madrid
Spain

Phone: +34-91-497-2412

Email: rdia...@gmail.com
   ramon.d...@iib.uam.es

http://ligarto.org/rdiaz

Re: [O] Remove Org from Emacs repository?

[Achim Gratz]

Reuben Thomas writes:
> ​Org is nearly 90kLOC, or about 6.5% of the total ELisp code currently in
> Emacs. It's bigger than CEDET, smaller than GNUS.

Within the whole of Emacs, an argument about size doesn't make any sense
at all.  It's also quite arbitrary, as some functionality that comes
with Org could or even should be factored out into their own packages
eventually.

> It's a project of its own with its own release cadence. It would be good to
> make Emacs less of a monolithic entity, which needs lengthy debugging
> cycles between releases, and has to choose between being out of date with
> various upstreams, or delaying to test integration of big packages.

That needs to be discussed with Emacs devs, not Org (or any other
package that fits a similar profile).  And it has been discussed in the
past, with somewhat interesting responses on both sides.

> Now that package.el is mature, there's no need for Emacs to include all
> this stuff in its source releases.

That assertion isn't universally accepted as true.  Org in particular
continues to show how the integration into Emacs as well as some
functionality in package.el itself is still lacking.  True packetization
of Emacs' "built-in" packages is further hindered by the fact that
package.el is currently solely "user-centric" and lacks the usual
facilities for curating package selection at the installation level.

> ​No, I was just testing the waters to see if a more modern approach to
> development and distribution might be popular. Apparently the answer is, at
> least, not yet!

Again, that's ultimately something for GNU Emacs to decide upon.  But it
doesn't come free nor is all the necessary infrastructure in place yet.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada