Re: Getting Org-Crypt to work (doc bug?)

2020-09-14 Thread Gregor Zattler
Hi David,
* David Masterson  [2020-09-13; 17:11]:
> Yes, gpg-agent is installed and appears to have been started in
> background.  My O/S is Debian on a Chromebook.
>
> I start Emacs via 'xterm -e emacs' and just noticed (thanks to you) that
> I'm getting a textual popup on the xterm asking for the
> passphrase. Given that, everything works.
>
> So, you're saying that the textual popup is the correct mechanism for
> getting the passphrase?

That's one possible way.  If you want to have a graphical
dialog box, check which pinentry packages are installed:

$ dpkg -l '*pinentry*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---==
un  pinentry  (no description available)
ii  pinentry-curses 1.1.0-2  amd64curses-based PIN or pass-phrase 
entry dialog for GnuPG
ii  pinentry-doc1.1.0-2  all  documentation for pinentry 
packages
un  pinentry-gnome3   (no description available)
un  pinentry-gtk2 (no description available)
ii  pinentry-qt 1.1.0-2  amd64Qt-based PIN or pass-phrase entry 
dialog for GnuPG
un  pinentry-qt4  (no description available)
un  pinentry-x11  (no description available)

as you see, at my system, there are two pinentry packages
installed (besides the docs): pinentry-curses for terminal
while pinentry-qt provides a graphical dialog box.  I choose
pinentry-qt, because it had fewer dependencies and was
smaller than the other options.

If your system lacks a graphical pinentry, install one.




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




Re: Getting Org-Crypt to work (doc bug?)

2020-09-13 Thread Gregor Zattler
Hi David,
* David Masterson  [2020-09-12; 19:09]:
> I'm trying to get org-crypt to work, but I'm missing something.
> Following the Org-Crypt Info page, I've set it up for symmetric
> encryption and added a :crypt: tag to a header.  When I try to save the
> file, it reports that no key was specified, so it will do symmetric
> encryption.  And then it freezes.  C-g will unfreeze, but the buffer is
> slightly messed up like it started working on something, but waited for
> an external command? GPG is installed.  What am I missing?

I assume it waits for a passphrase.  Do you have gpg-agent
installed?  What is your operating system?


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




Re: [bug] error on RET in read-only buffer with org-return-follows-link set to t

2020-05-15 Thread Gregor Zattler
Hi Nicolas, Kévin,

thanks to both of you: It works again for me.

Ciao; Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-
* Nicolas Goaziou  [2020-05-15; 00:49]:
> Kévin Le Gouguec  writes:
>
>> Shouldn't the call to org-return be wrapped in (call-interactively …)
>> though?
>
> Indeed. Done. Thank you.




[bug] error on RET in read-only buffer with org-return-follows-link set to t

2020-05-14 Thread Gregor Zattler
Dear Kévin, org-mode developers, 

with `org-return-follows-link` set to `t` in a read-only
buffer I now get a `Buffer is read-only: #` error when pressing ENTER/RETURN
with point on an org-mode link.

This used to work (opening the org-mode link) till

d3e6b58004997c5a9eeea82f96723c0f74480ab8 is the first bad commit
commit d3e6b58004997c5a9eeea82f96723c0f74480ab8
Author: Kévin Le Gouguec 
Date:   Tue May 5 19:01:07 2020 +0200

Make RET and C-j obey `electric-indent-mode'

* lisp/org-compat.el (org-return-indent): Deprecate this command.
* lisp/org-keys.el (org-mode-map): Rebind C-j to a command emulating
`electric-newline-and-maybe-indent'.
* lisp/org.el (org-cdlatex-environment-indent): Stop using the now
obsolete function.
(org--newline): New helper function.
(org-return): Use it to transparently handle `electric-indent-mode'.
(org-return-and-maybe-indent): New command to emulate
`electric-newline-and-maybe-indent' while taking care of Org special
cases (tables, links, timestamps).
* testing/lisp/test-org.el (test-org/with-electric-indent,
test-org/without-electric-indent): New tests.
* testing/org-test.el (org-test-with-minor-mode): New helper to set a
minor mode to a specific state, and reset it afterward.

:04 04 85f261b701133d4be047c1a2e8872b25f3e0c7e7 
21fe88d69e48ac3d24d233cbf07fe0084cde853e M  etc
:04 04 a677d2134361d2b023f252c188aebdeef9826896 
4bdbb34abe7eaad343932d33a03c823b2cae0e24 M  lisp
:04 04 9ecba96d2748f0e7ff5430ec0fcf8c175875621f 
f6e7b54445ac19d1b7c59d4d54bd9b4a19126245 M  testing


I use this dozens of times a day and it would be convenient
if it was possible to resurrect the old behaviour.


Thanks for your attention and for developing org-mode,
Gregor 
-- 
 -... --- .-. . -.. ..--.. ...-.-




[PATCH] org-screen.el: replace obsolete function

2019-12-15 Thread Gregor Zattler
* contrib/lisp/org-screen.el (org-screen): replace obsolete function
`insert-string' with `insert'.
---
 contrib/lisp/org-screen.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/lisp/org-screen.el b/contrib/lisp/org-screen.el
index 6b870f229..948e93adf 100644
--- a/contrib/lisp/org-screen.el
+++ b/contrib/lisp/org-screen.el
@@ -64,7 +64,7 @@
   (interactive "MScreen name: ")
   (save-excursion
 (org-screen-helper name "-S"))
-  (insert-string (concat "[[screen:" name "]]")))
+  (insert (concat "[[screen:" name "]]")))

 (defun org-screen-buffer-name (name)
   "Returns the buffer name corresponding to the screen name given."
--
2.11.0




Re: [O] Compile failure

2019-06-25 Thread Gregor Zattler
Hi Eric, Klaushal,
* "Fraga, Eric"  [2019-06-24; 18:04]:
> On Monday, 24 Jun 2019 at 11:48, Kaushal Modi wrote:
>> That issue on Emacs master is fixed now for me.
>
> If it happens not to be, for Bill: just go to your emacs and
>
>  git checkout 63b29f81075a3fdca70348f023d3ebb37a4f2a63

I assume you both know this will pin your git repo to this very
commit.

If one wants to use the emacs development version it's better to
do

git pull
git co -f master

an you will use cutting edge of emacs development.



>  make clean
>  make && make install
>
> and things should work.  They do for me.
Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-




[O] [PATCH] * doc/org-manual.org (External Links): Fix URL

2019-06-01 Thread Gregor Zattler


---
 doc/org-manual.org | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 469e16402..583840a74 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -3081,7 +3081,7 @@ External links are URL-like locators.  They start with a 
short
 identifying string followed by a colon.  There can be no space after
 the colon.  The following list shows examples for each link type.

-| =http://www.astro.uva.nl/=dominik=| on the web |
+| =https://staff.science.uva.nl/c.dominik/= | on the web |
 | =doi:10.1000/182= | DOI for an electronic resource |
 | =file:/home/dominik/images/jupiter.jpg=   | file, absolute path|
 | =/home/dominik/images/jupiter.jpg=| same as above  |
--
2.11.0




Re: [O] [RFC] org-style

2019-05-10 Thread Gregor Zattler
Hi Marco, org-mode developers and users,
* Marco Wahl  [2019-05-10; 13:55]:

> What do you think about this?  Is this worth to merge into org mode?

This is nice, I played with it and see it's merit, but I think
this should not be enabled by default.

Even if the user had to enable it first via customization, this
version of the code has another drawback: if it actually touches
the buffer in order to change the number of blank lines it at the
same time removes the indentation of the first non blank line.
This might not be what the user wishes and should either not be
the case or also disabled per default:

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




Re: [O] Logging :LOGBOOK: entries to a heading in org-mode without TODO state changes

2019-04-09 Thread Gregor Zattler
Hi Daryl,
* Daryl Manning  [2019-04-08; 22:46]:
> I have org-mode set up at the moment to log changes in my TODO states (at
> the moment, TODO, CHASE, GAVE, KILL, DONE) as well as deadline changes and

would you please elaborate on the semantics of these (esp. chase,
gave)?

> reschedules into a logbook drawer. That's working great.
>
> However, I have begun using org-contacts as an ersatz CRM for myself and
> keeping track of mails, meets, and other administrivia tracking people I'm
> interacting with.
>
> I'd love to have a way to as easily use something CTRL-C-T and then have
> the ability to log an item into a Logbook drawer under each
> heading name.

There's org-add-note, bound by default to C-c C-z, which does
exactly that.  It even works from the agenda.

> Is there a way to do this easily without hacking TODO states? Or are there
> other ways people are doing this to achieve the same goal (I'm also hoping
> to set PING deadlines on people so that I am making sure to recontact them
> at various intervals over time, but still trying to puzzle that out... =]
> ).

I tried to use org-habit for this, but it gets clumsy, if you
want to contact somebody round about every 60 days or so.


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




[O] orgalist-mode: wrong indentation in message mode after recent change in emacs

2019-04-01 Thread Gregor Zattler
Dear org-mode developers, hello Nicolas,
 I use orgalist-mode while writing emails in
 notmuch-message-mode.  Today I updated emacs (from git), and
 since then, the second line of a paragraph get's indented
 (and succeeding lines too).

As demonstrated with this email.  While I write this email with
   my configurations, I checked with emacs -Q as follows: visited
   one org file (in order for org-mode to load), visited
   orgalist.el, eval'ed this buffer and started writing an email:
   bang! indented succeeding lines.



I bisected emacs like so:

make ; src/emacs -Q --eval '(org-mode)' -l 
~/.emacs.d/elpa-27.0/orgalist-1.9/orgalist.el -f compose-mail --eval 
'(orgalist-mode)' -f end-of-buffer


and this is the relevant commit:

2e3deb09bd42d22a9b354937ce63b151fb493d8a is the first bad commit
commit 2e3deb09bd42d22a9b354937ce63b151fb493d8a
Author: Basil L. Contovounesios 
Date:   Sun Mar 31 19:39:54 2019 +0100

Do not set indent-line-function in text-mode

For discussion, see thread starting at:
https://lists.gnu.org/archive/html/emacs-devel/2019-03/msg01012.html
* lisp/textmodes/text-mode.el (text-mode): Do not reset
indent-line-function to its global default value of indent-relative.
* doc/lispref/modes.texi (Example Major Modes):
* etc/NEWS: Document change accordingly.

:04 04 88d3790ae5446f2ef84b66733c2b9e9bd27676a8 
53a988cc46c8505b5751120b6f0813c5f252b171 M  doc
:04 04 0f12bd57efcc2a481b468ecefb0369ef3b3996c9 
055f07d1469cee692acc35ba9ce5ec2611a6f7db M  etc
:04 04 0c34b9e6e31c833a7c3c4e464e0ccbf597156850 
d330f001af22700ec84b0d1596571fa4548eafa8 M  lisp


I do not know what to do with this.


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




Re: [O] Multiple Indices

2019-03-02 Thread Gregor Zattler
Hi Robert,
* Robert Love  [2019-03-02; 16:29]:
> I don’t understand this advice.   I went looking for the source
> for the Org manual and found it IS written in Texinfo. This
> is version 8.2.10.   Is there a native Org mode manual written
> in Org?

Yes since version 9 I think.  It will be part of emacs when a
newer version is bundled with a released version of emacs. 

> If so, please provide the source location.

In the mean time:
https://code.orgmode.org/bzg/org-mode/raw/master/doc/org-manual.org

Ciao; Gregor 




Re: [O] Multiple Indices

2019-03-01 Thread Gregor Zattler
Hi Robert,
* Robert Love  [2019-02-28; 23:52]:
> I’m using Org mode to document some software.  When I see
> Texinfo used for this, I see that you can have a subject index
> and a variable index.  How do I achieve the same thing in Org
> mode?  Can someone point to examples of this?

I don't know anything about texinfo, but the Org-mode manual has
three indices.  You may have a look at doc/org-manual.org.

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




Re: [O] [bug/regression]: org-babel-load-file gives error: wrong-type-argument listp "/home/grfz/.emacs.d/configuration.org"

2019-01-14 Thread Gregor Zattler
Hi Kyle, org-mode developers,
* Kyle Meyer  [2019-01-14; 17:10]:
> Kyle Meyer  writes:
>> Gregor Zattler  writes:
> [...]
>
>>> I did a git bisect on the org repo and got this:
>>> ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit
>>
>> Sorry, that certainly looks to be my fault (specifically, my conflict
>> resolution merging maint's d64c9a996).  I'll have a look.
>
> Fixed by baa98a4a6fe93dd99fb624ad218fb3e1868cfde3.

Thank you very much for the quick fix.  It works again.

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




[O] [bug/regression]: org-babel-load-file gives error: wrong-type-argument listp "/home/grfz/.emacs.d/configuration.org"

2019-01-14 Thread Gregor Zattler
Dear org-mode developers, I did a git pull half an hour ago, now I
cannot org-babel-load-file my configuration.org any more.  Normally I
use emacs as of git master but the (slightly different) error also
occours with emacs 25.1.1 (as of currents debian stable) (see below).

I did a git bisect on the org repo and got this:
ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit


Thanks for your attention and your work on org-mode, Gregor


emacs 251.1:
File Edit Options Buffers Tools Debugger Help   

   
Debugger entered--Lisp error: (wrong-type-argument listp 
"/home/grfz/.emacs.d/configuration.org")

  
  nth(5 "/home/grfz/.emacs.d/configuration.org")

   
  file-attribute-modification-time("/home/grfz/.emacs.d/configuration.org") 

   
  (org-file-newer-than-p tangled-file (file-attribute-modification-time file))  

   
  (if (org-file-newer-than-p tangled-file (file-attribute-modification-time 
file)) nil (org-babel-tangle-file file tangled-file "emacs-lisp"))  

   
  (let* ((tangled-file (concat (file-name-sans-extension file) ".el"))) (if 
(org-file-newer-than-p tangled-file (file-attribute-modification-time file)) 
nil (org-babel-tangle-file file tangled-file "emacs-lisp")) (if compile (progn 
(byte-$
  org-babel-load-file("/home/grfz/.emacs.d/configuration.org")  

   
  mapc(org-babel-load-file ("/home/grfz/.emacs.d/configuration.org"))   

   
  eval-buffer(# nil "/home/grfz/.emacs.d/init.el" nil t)  ; 
Reading at buffer position 7565 

   
  load-with-code-conversion("/home/grfz/.emacs.d/init.el" 
"/home/grfz/.emacs.d/init.el" t t)  

 
  load("/home/grfz/.emacs.d/init" t t)  

   
  #[0 "^H\205\266^@ \306=\203^Q^@\307^H\310Q\202?^@ 
\311=\204^^^@\307^H\312Q\202?^@\313\307\314\315#\203*^@\316\202?^@\313\307\314\317#\203>^@\320\321\322!D\nB^R\323\202?^@\316\324^S\325^A\324\211#\210^K\324=\203e^@\326\327\330\307^H\$
  command-line()

   
  normal-top-level()


emacs 27:
Debugger entered--Lisp error: (wrong-type-argument listp 
"/home/grfz/.emacs.d/configuration.org")

  
  file-attribute-modification-time("/home/grfz/.emacs.d/configuration.org") 

   
  (org-file-newer-than-p tangled-file (file-attribute-modification-time file))  

   
  (if (org-file-newer-than-p tangled-file (file-attribute-modification-time 
file)) nil (org-babel-tangle-file file tangled-file "emacs-lisp"))  

   
  (let* ((tangled-file (concat (file-name-sans-extension file) ".el"))) (if 
(org-file-newer-than-p tangled-file 

Re: [O] Tasks performed on a certain day

2018-11-09 Thread Gregor Zattler
Hi Nicolas, org mode users and developers,
* Nicolas Goaziou  [2018-11-08; 18:34]:
> However, I think some users need to have multiple so-called events in
> the same headline, e.g., for irregularly repeating tasks.

Yes, I do this all the time.  For instance there is a heading for
visits at the dentist in my org file which contains plain
timestamps for every day I went there.  This is quite handy as
I'm able to tell when I was there with a glance at this list of
plain stamps.  This may be helpful when dealing with the
insurance company.

If a heading could only hold one event timestamp I would need
much more headings which look somewhat heavy because of the
markup, the way they are shown and most probably would also
feature a drawer each .  OTHT I could then archive all old visits
at the dentist, have a smaller org file but it would be more
difficult to reconstruct past dates with my dentist.  Because
then they would be scattered among other headings in the archive
file and the only way of finding out would be to generate an
agenda from the archive file.


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




[O] Bug: manual still mentions orgstruct minor mode [9.1.14 (release_9.1.14-968-gfdb36d @ /home/grfz/src/org-mode/lisp/)]

2018-10-06 Thread Gregor Zattler
Dear org mode developers,

orgstruct minor mode is still mentioned as an usage example for
in-place conversion in org manuals chapter "12.18 Export in
Foreign Buffers".

I know and use package "orgalist" but I'm not sure if it makes
sense to mention a package at this point of the org manual.
Furthermore I do not use in-place conversions, therefore I cannot
propose another example/wordoing.


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




Re: [O] need help with repeated tasks (won't reapeat)

2018-08-19 Thread Gregor Zattler
Hi Marco, org mode users,
* Marco Wahl  [2018-08-19; 13:46]:
> Gregor Zattler  writes:
>
>> Dear org mode users, I have problems with a repeated task.  I
>> want to clean something round about every 60 days.  I set up this
>> task in order to monitor my cleaning:
>>
>>
>> *** TODO Clean it
>> DEADLINE:<2018-08-12 So +.60d -9d>
>
> How about toggling the plus and the dot like so?
>
> DEADLINE:<2018-10-18 .+60d -9d>

You are spot on, this was the mistake I made and did not realize
although I reread the relevant manual section...

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





[O] need help with repeated tasks (won't reapeat)

2018-08-19 Thread Gregor Zattler
Dear org mode users, I have problems with a repeated task.  I
want to clean something round about every 60 days.  I set up this
task in order to monitor my cleaning:


*** TODO Clean it
DEADLINE:<2018-08-12 So +.60d -9d>
:PROPERTIES:
:LAST_REPEAT: [2018-05-30 Mi 16:01]
:REPEAT_TO_STATE: TODO
:END:
:LOGBOOK:
- State "DONE"   from "TODO"   [2018-05-30 Mi 16:01]
- State "DONE"   from "TODO"   [2018-03-26 Mo 16:47]
:END:


But when I do a C-c C-t (org-agenda-todo) with point on the
heading or on the corresponding line in the agenda, the task
switches simply to DONE and that's it.  It doesn't switch back to
TODO, the deadline is not shifted:

*** DONE Clean it
DEADLINE:<2018-08-12 So +.60d -9d>
:PROPERTIES:
:LAST_REPEAT: [2018-05-30 Mi 16:01]
:REPEAT_TO_STATE: TODO
:END:
:LOGBOOK:
- State "DONE"   from "TODO"   [2018-05-30 Mi 16:01]
- State "DONE"   from "TODO"   [2018-03-26 Mo 16:47]
:END:


I would expect the TODO State to shift back to TODO and the
deadline base date to be shifted by 60 days from today.


My problems persist if I test this with emacs -Q with these two
versions of emacs and org-mode

GNU Emacs 25.1.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.11) of 2017-09-15, 
modified by Debian
Org-mode version 8.2.10 (release_8.2.10 @ /usr/share/emacs/25.1/lisp/org/)

GNU Emacs 27.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version 3.22.11) of 
2018-08-17
Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ 
/usr/local/stow/emacs-snapshot/share/emacs/27.0.50/lisp/org/)


and with this newer org mode version but with my configurations
loaded:

GNU Emacs 27.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version 3.22.11) of 
2018-08-17
Org mode version 9.1.13 (release_9.1.13-898-gab1f77 @ 
/home/grfz/src/org-mode/lisp/)



Since this is really basic usage I assume no bug but some error
on my side.  What am I doing wrong?



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




[O] do not ignore mdc errors on a permanent basis (was: org-crypt broken on Ubuntu 18.04)

2018-07-26 Thread Gregor Zattler
Hi Óscar,
* Óscar Fuentes  [2018-07-26; 13:57]:
> For the record: executing gpg2 from the command line is revealing:
>
> gpg: WARNING: message was not integrity protected
> gpg: Hint: If this message was created before the year 2003 it is
>  likely that this message is legitimate.  This is because back
>  then integrity protection was not widely used.
> gpg: Use the option '--ignore-mdc-error' to decrypt anyway.
> gpg: decryption forced to fail!
>
> The solution is to add `ignore-mdc-error' to ~/.gnupg/gpg.conf.

I hope you'll do this only as a temporary meassure.  Your could
decrypt and re-encrypt the org-crypt parts in question iff you
are sure, they were encrypted years ago and their contents is ok.

But having this option in  ~/.gnupg/gpg.conf  otherwise weakens
the security of GnuPG usage considerably.

>From the gpg man page:

 --ignore-mdc-error
  This option changes a  MDC integrity protection failure
  into a  warning.  This  can be useful  if a  message is
  partially corrupt, but  it is necessary to  get as much
  data as possible out  of the corrupt message.  However,
  be aware  that a MDC  protection failure may  also mean
  that the message was  tampered with intentionally by an
  attacker.

The usage scenario described in the first sentence is clearly a
one time thing.  Putting this option in gpg.conf ignores these
kind of errors for all future usage, for risks and side effects
see the second sentence.

Ciao; Gregor 




Re: [O] Tag completion does not work well with org-complete-tags-always-offer-all-agenda-tags

2018-05-12 Thread Gregor Zattler
Hi Alain,
* alain.coch...@unistra.fr [2018-05-12; 08:32]:
> I got:
>
> Emacs : GNU Emacs 24.5.1 (x86_64-redhat-linux-gnu, GTK+ Version
> 3.18.9) of 2016-04-11 on buildvm-25.phx2.fedoraproject.org Package:
> Org mode version 9.1.13 (release_9.1.13-744-g13fb6a @
> /home/cochard/Org/Coch-git/org-mode/lisp/)
>
> Is that the master branch?

Seems so.

> Did you mean 'emacs -Q' with some git branch?  If so, I don't know how
> to do it...

emacs -Q -L /home/cochard/Org/Coch-git/org-mode/lisp/ 

which ads git Org to the load-path 

perhaps even

emacs -Q -L /home/cochard/Org/Coch-git/org-mode/lisp/ -l 
/home/cochard/Org/Coch-git/org-mode/lisp/org.el 

which even loads Org mode.

You could write a small file with the necessary settings and load
it also 

emacs -Q -L /home/cochard/Org/Coch-git/org-mode/lisp/ -l 
/home/cochard/Org/Coch-git/org-mode/lisp/org.el -l /tmp/minimal-exaple.el

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




Re: [O] [RFC] Dog food, anyone?

2018-05-09 Thread Gregor Zattler
Hi Nicolas, Org mode developers,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-05-09; 02:30]:
> Bastien <b...@gnu.org> writes:
>
>> it would be nice to make the switch to org-manual.org for Org 9.2,
>> and to delete org.texi entirely from the master branch.
>
> Done.
>
>> I guess we need to add some Makefile rules so that "make pdf" first
>> exports .org => .texi then exports .texi to .pdf... is that so?
>
> Done (or so I think).

Hurray!

I found that org-float instead of diary-float is documented in
org-manual.org although ORG-NEWS says to use diary-float instead:

~/src/org-mode$ rgrep  org-float
etc/ORG-NEWS:** =org-float= is now obsolete, use =diary-float= instead
Binary file lisp/org-compat.elc matches
lisp/org-compat.el:(define-obsolete-function-alias 'org-float-time 'float-time 
"Org 9.0")
testing/lisp/test-org.el:   (org-test-with-temp-text "<%%(org-float t 4 2)>"
testing/lisp/test-org.el:   (equal "<%%(org-float t 4 2)>"
testing/lisp/test-org.el: (org-test-with-temp-text "<%%(org-float t 4 
2)>"
doc/org.texi:  <%%(org-float t 4 2)>
doc/org.texi:<%%(org-float t 42)>
doc/org-manual.org:   <%%(org-float t 4 2)>
doc/org-manual.org:: <%%(org-float t 42)>
doc/org:<%%(org-float t 4 2)>
doc/org: <%%(org-float t 42)>
doc/org.html:  %%(org-float t 4 2)
doc/org.html:%%(org-float t 42)


~/src/org-mode$ rgrep  diary-float
etc/ORG-NEWS:** =org-float= is now obsolete, use =diary-float= instead
testing/lisp/test-org-element.el:  (should (equal (org-test-parse-and-interpret 
"<%%diary-float t 4 2>")
testing/lisp/test-org-element.el:"<%%diary-float t 4 2>\n"))
doc/orgguide.texi:  <%%(diary-float t 4 2)>

org-guide.texi is already up to date with respect to
diary-float.

I made a very simple patch for org-manual.org but none for
test-org.el or test-org-element.el since I do not understand
them.  When reading about documentation standards I found that
Org manuals filename and directory wasn't up to date, so I fixed
this.  I assume that the parts of doc/Documentation_Standards.org
which deal with texinfo formatting are also out of date but do
not know how to rewrite them.

>From b45739a23b093e1ee54ae09be8172720fa611628 Mon Sep 17 00:00:00 2001
From: Gregor Zattler <telegr...@gmx.net>
Date: Wed, 9 May 2018 19:51:51 +0200
Subject: [PATCH] ; Tiny doc fixes

* doc/org-manual.org (Dates and Times) (Timestamps, Deadlines and
  Scheduling): Document "diary-float" instead of obsolete "org-float".
* doc/Documentation_Standards.org (org-manual.org specific
  conventions): Fix file name and directory of Org manual.

Copyright-paperwork-exempt: yes
TINYCHANGE
---
 doc/Documentation_Standards.org | 4 ++--
 doc/org-manual.org  | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/Documentation_Standards.org b/doc/Documentation_Standards.org
index 9d8f19fe6..c4dd862db 100644
--- a/doc/Documentation_Standards.org
+++ b/doc/Documentation_Standards.org
@@ -94,10 +94,10 @@ I have made them up of course).
 - Entries in the concept index are normally all lower case unless some
   other rule dictates otherwise.
 
-* orgmanual.org specific conventions
+* org-manual.org specific conventions
 
 Org git repository comes with an .org version of the manual in the
-=contrib/= directory.  Here are indications that are specific to this
+=doc/= directory.  Here are indications that are specific to this
 version of the manual.
 
 - Five of the standard Texinfo indexes are used in the Org manual:
diff --git a/doc/org-manual.org b/doc/org-manual.org
index eb6c96fb2..d9e95b1ee 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -5779,7 +5779,7 @@ the agenda (see [[*Weekly/daily agenda]]).  We distinguish:
 
  #+begin_example
  ,* 22:00-23:00 The nerd meeting on every 2nd Thursday of the month
-   <%%(org-float t 4 2)>
+   <%%(diary-float t 4 2)>
  #+end_example
 
 - Time/Date range ::
@@ -6158,7 +6158,7 @@ entries.  Org mode issues early and late warnings based on the
 assumption that the timestamp represents the /nearest instance/ of the
 repeater.  However, the use of diary S-exp entries like
 
-: <%%(org-float t 42)>
+: <%%(diary-float t 42)>
 
 #+texinfo: @noindent
 in scheduling and deadline timestamps is limited.  Org mode does not
-- 
2.11.0


I'm not sure if "org-float" is the right way to quote this kind
of symbol in a commit message.  Please fix if not.

HTH a tiny bit, Gregor



Re: [O] Orgalist notes

2018-05-08 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-05-07; 22:29]:
> Gregor Zattler <telegr...@gmx.net> writes:
>
>> Yes, I used the customization interface and choose "2)".  [This
>> produces 41 as value of this variable.  I did so, because
>> sometimes a sentence ends in a number and a period but these
>> happen to be after a auto-fill line break and org would assume
>> it's a list, indenting the following lines.
>
[...]
> This shouldn't happen. Org has guards against this kind of auto
> filling.

OK.  Back then, when I customized this I used fill-adapt-mode, perhaps this
was the culpruit.  I do not use it anymore so after this test I
will switch it to t and see what happens.   Thanks for this hint.

>> And I now see, orgalist does not recognize
>>
>> 1) as a list.  Neither does it indent succeeding lines after the
>> first one, nor begin a new numbered item after M-RET
>>
>> If it's not possible to use "2)", then perhaps this should be
>> documented?
>
> This is documented. In `orgalist-mode' docstring:
>
>   When Orgalist mode is enabled, any line beginning with "-", "+", "1."
>   or "a." followed by a space starts a list.
>
> However, setting `org-plain-list-ordered-item-terminator' for Org mode
> should not affect Orgalist minor mode. IOW, activating Orgalist should
> set the variable to ?. unconditionally.
>
> So... here comes Orgalist 1.7.

1. zhfsiu zhuihg uidzhrg idzhg uidhr ihgi udhrg kuidh giudrhui
   tgui ui h iM-RET
2. hae foihfje ohfe oirh gesellschaftlich


Works now without a glitch!

Thanks a bundle for your fast help.

Ciao; Gregor 




Re: [O] Orgalist notes

2018-05-07 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-05-07; 19:32]:
> Gregor Zattler <telegr...@gmx.net> writes:
>
>> Sure:
>>
>> 1. hdf ds gjdfg dzg vizdgvzu uid vjudgfvkjui dkjui uiv dfu du
>>sjuds gdhfj dhfg vhjf df dfkjh vkjM-RET
>
> Do you have `org-plain-list-ordered-item-terminator' set to ?\) ?

Yes, I used the customization interface and choose "2)".  This
produces 41 as value of this variable.  I did so, because
sometimes a sentence ends in a number and a period but these
happen to be after a auto-fill line break and org would assume
it's a list, indenting the following lines.

And I now see, orgalist does not recognize

1) as a list.  Neither does it indent succeeding lines after the
first one, nor begin a new numbered item after M-RET

If it's not possible to use "2)", then perhaps this should be
documented?

Thanks for your help, Gregor




Re: [O] Orgalist notes

2018-05-07 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou  [2018-05-07; 14:37]:
> I cannot reproduce the issue. It seems to be with "org-list.el".
>
> Could you do it again, this time after loading Org uncompiled? I need
> the backtrace to step into `org-list-insert-item'.

Sure:

1. hdf ds gjdfg dzg vizdgvzu uid vjudgfvkjui dkjui uiv dfu du
   sjuds gdhfj dhfg vhjf df dfkjh vkjM-RET


Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  goto-char(nil)
  (progn (goto-char pos) (goto-char (org-list-get-item-begin)))
  (let* ((item (progn (goto-char pos) (goto-char (org-list-get-item-begin 
(item-end (org-list-get-item-end item struct)) (item-end-no-blank 
(org-list-get-item-end-before-blank item struct)) (beforep (progn (looking-at 
org-list-full-item-re) (<= pos (cond ((not (match-beginning 4)) (match-end 0)) 
((let ((save-match-data-internal (match-data))) (unwind-protect (progn 
(string-match "[.)]" (match-string 1))) (set-match-data 
save-match-data-internal 'evaporate))) (match-beginning 4)) (t (save-excursion 
(goto-char (match-end 4)) (skip-chars-forward " \11") (point))) 
(split-line-p (org-get-alist-option org-M-RET-may-split-line 'item)) (blank-nb 
(org-list-separating-blank-lines-number pos struct prevs)) (ind 
(org-list-get-ind item struct)) (ind-size (if indent-tabs-mode (+ (/ ind 
tab-width) (mod ind tab-width)) ind)) (bullet (org-list-bullet-string 
(org-list-get-bullet item struct))) (box (if checkbox (progn "[ ]"))) (text-cut 
(and (not beforep) split-line-p (progn (goto-char pos) (if (< item-end pos) 
(progn (delete-region (1- item-end) (point-at-eol (skip-chars-backward " 
\15\11\n") (setq pos (point)) (delete-and-extract-region pos 
item-end-no-blank (body (concat bullet (if box (progn (concat box " "))) 
after-bullet (and text-cut (if (string-match "\\`[ \11]+" text-cut) 
(replace-match "" t t text-cut) text-cut (item-sep (make-string (1+ 
blank-nb) 10)) (item-size (+ ind-size (length body) (length item-sep))) 
(size-offset (- item-size (length text-cut (goto-char item) 
(indent-to-column ind) (insert body item-sep) (mapc (function (lambda (e) (let 
((p (car e)) (end (nth 6 e))) (cond ((< p item) (if (> end item) (progn (setcar 
(nthcdr 6 e) (+ end size-offset) ((or beforep (not split-line-p)) (setcar e 
(+ p item-size)) (setcar (nthcdr 6 e) (+ end item-size))) ((< p pos) (setcar e 
(+ p item-size)) (if (< end pos) (setcar (nthcdr 6 e) (+ end item-size)) 
(setcar (nthcdr 6 e) (+ end size-offset ((< p item-end) (setcar e (+ p 
size-offset (- item pos (length item-sep (if (= end item-end) (setcar 
(nthcdr 6 e) (+ item item-size)) (setcar (nthcdr 6 e) (+ end size-offset (- 
item pos (length item-sep)) (t (setcar e (+ p size-offset)) (setcar (nthcdr 
6 e) (+ end size-offset))) struct) (setq struct (cons (list item ind bullet 
nil box nil (+ item item-size)) struct)) (setq struct (sort struct (function 
(lambda (e1 e2) (< (car e1) (car e2)) (if beforep (goto-char item) (setq 
struct (org-list-swap-items item (+ item item-size) struct)) (goto-char 
(org-list-get-next-item item struct (org-list-prevs-alist struct struct)
  (let ((case-fold-search t)) (let* ((item (progn (goto-char pos) (goto-char 
(org-list-get-item-begin (item-end (org-list-get-item-end item struct)) 
(item-end-no-blank (org-list-get-item-end-before-blank item struct)) (beforep 
(progn (looking-at org-list-full-item-re) (<= pos (cond ((not (match-beginning 
4)) (match-end 0)) ((let ((save-match-data-internal (match-data))) 
(unwind-protect (progn (string-match "[.)]" (match-string 1))) (set-match-data 
save-match-data-internal 'evaporate))) (match-beginning 4)) (t (save-excursion 
(goto-char (match-end 4)) (skip-chars-forward " \11") (point))) 
(split-line-p (org-get-alist-option org-M-RET-may-split-line 'item)) (blank-nb 
(org-list-separating-blank-lines-number pos struct prevs)) (ind 
(org-list-get-ind item struct)) (ind-size (if indent-tabs-mode (+ (/ ind 
tab-width) (mod ind tab-width)) ind)) (bullet (org-list-bullet-string 
(org-list-get-bullet item struct))) (box (if checkbox (progn "[ ]"))) (text-cut 
(and (not beforep) split-line-p (progn (goto-char pos) (if (< item-end pos) 
(progn (delete-region (1- item-end) (point-at-eol (skip-chars-backward " 
\15\11\n") (setq pos (point)) (delete-and-extract-region pos 
item-end-no-blank (body (concat bullet (if box (progn (concat box " "))) 
after-bullet (and text-cut (if (string-match "\\`[ \11]+" text-cut) 
(replace-match "" t t text-cut) text-cut (item-sep (make-string (1+ 
blank-nb) 10)) (item-size (+ ind-size (length body) (length item-sep))) 
(size-offset (- item-size (length text-cut (goto-char item) 
(indent-to-column ind) (insert body item-sep) (mapc (function (lambda (e) (let 
((p (car e)) (end (nth 6 e))) (cond ((< p item) (if (> end item) (progn (setcar 
(nthcdr 6 e) (+ end size-offset) ((or beforep (not split-line-p)) (setcar e 
(+ p item-size)) (setcar (nthcdr 6 

Re: [O] Orgalist notes

2018-05-07 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-05-06; 13:32]:
> Gregor Zattler <telegr...@gmx.net> writes:
>
>> With org-mode in the load-path, the line breaks happen for all
>> lines not only the first one.  But one has to (require 'org) in
>> order for M-RET to work.  This is no problem for me, since I work
>> with org-mode all the time, but is this intended?
>
> No, it is not intended. Orgalist 1.6 (to be released tomorrow) will
> require Org right from the start.

This works now with bullet and numbered lists when called in a
non-configured emacs session.  Thanks.


>> In my highly customized emacs I get line breaks but M-RET gives
>>
>> 1. jesdgf oigjovgjis uh urh udrhfesgh ourhes ouh ouhroe uhos ho
>>hg uirehui shgourheoug hhsou hogush oguhuishughsoieghoudrhes
>>uhguhdsh ghourhg
>>
>> orgalist-insert-item: Wrong type argument: integer-or-marker-p, nil
[...]
>> Could you give me a hint on how to debug this?
>
> Please use M-x toggle-debug-on-error and report the backtrace here.
> Loading an un-compiled Orgalist is better.

1. rzhe juhgdhjvhj vghfjs y rvgfhjxd bvjxdbv mh vxnbxgbfvghg drgh
   djhxcjhbnjdfjhvgjhf jhfhjghfj hfjM-RET


gives:

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  org-list-insert-item(1504 ((1397 0 "1. " nil nil nil 1505)) ((1397)) nil nil)
  (setq struct (org-list-insert-item (point) struct prevs checkbox desc))
  (let* ((struct (save-excursion (goto-char item\?) (orgalist--struct))) (prevs 
(org-list-prevs-alist struct)) (desc (and (eq 'descriptive 
(org-list-get-list-type item\? struct prevs)) " :: "))) (setq struct 
(org-list-insert-item (point) struct prevs checkbox desc)) 
(org-list-write-struct struct (org-list-parents-alist struct)) (looking-at 
orgalist--item-re) (goto-char (if (and (match-beginning 4) (let 
((save-match-data-internal (match-data))) (unwind-protect (progn (string-match 
"\\." (match-string 1))) (set-match-data save-match-data-internal 
'evaporate (match-beginning 4) (match-end 0))) (if desc (progn 
(backward-char 1
  (let ((item\? (orgalist--in-item-p))) (if item\? nil (user-error "Not in a 
list")) (let* ((struct (save-excursion (goto-char item\?) (orgalist--struct))) 
(prevs (org-list-prevs-alist struct)) (desc (and (eq 'descriptive 
(org-list-get-list-type item\? struct prevs)) " :: "))) (setq struct 
(org-list-insert-item (point) struct prevs checkbox desc)) 
(org-list-write-struct struct (org-list-parents-alist struct)) (looking-at 
orgalist--item-re) (goto-char (if (and (match-beginning 4) (let 
((save-match-data-internal (match-data))) (unwind-protect (progn (string-match 
"\\." (match-string 1))) (set-match-data save-match-data-internal 
'evaporate (match-beginning 4) (match-end 0))) (if desc (progn 
(backward-char 1)
  orgalist-insert-item(nil)
  funcall-interactively(orgalist-insert-item nil)
  call-interactively(orgalist-insert-item nil nil)
  command-execute(orgalist-insert-item)


I have no clue how to read this.


Thanks for looking into this, Gregor




Re: [O] Orgalist notes

2018-05-06 Thread Gregor Zattler
Hi Eric, Nicolas,
* Eric Abrahamsen  [2018-05-05; 16:55]:
> - And before I get tired of the experiment, here's the same thing with
>  a numbered list.
> - Oh damn, I hit M-RET, and the numbered list turned into an unnumbered
>   list.

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


I get


1. ha fkj hdhf kjh kdjfh kdjsh gjhdlkj ghkjdsgh dj ljgh kjdh kjhvgfkj
   hdgkjhkjh djhg kjdhf kjhdkjghf kdhödgkhödkj hödj öh ödfkj hökhdgfsjh kjgh dh 
hdgöf h h ö ökhkjhgdöhg jdhf kj ök ökdfj ödfj dfjkj kjg kj kjdökgh ödh öhg   g  
g   

   - no autofill after the second line
   - M-RET gives: setq: Symbol’s function definition is void:
 org-in-regexp



With org-mode in the load-path, the line breaks happen for all
lines not only the first one.  But one has to (require 'org) in
order for M-RET to work.  This is no problem for me, since I work
with org-mode all the time, but is this intended?


In my highly customized emacs I get line breaks but M-RET gives

1. jesdgf oigjovgjis uh urh udrhfesgh ourhes ouh ouhroe uhos ho
   hg uirehui shgourheoug hhsou hogush oguhuishughsoieghoudrhes
   uhguhdsh ghourhg

orgalist-insert-item: Wrong type argument: integer-or-marker-p, nil

This is not the case with bullet lists:

- o ushurgh dusrh gdrhf oudrhesurgh urhrh oughou hortus houtgsh
  ou houhort rtgshM-RET
- 


Could you give me a hint on how to debug this?


Thanks, Gregor




Re: [O] Orgalist notes

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

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

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

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

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


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


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




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

2018-04-27 Thread Gregor Zattler
Hi Nicolas, org-mode users,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-04-27; 15:13]:
> Gregor Zattler <telegr...@gmx.net> writes:
>> +It's possible to use different keys for different headings by
>> +specifying the respective key as property CRYPTKEY, e.g.:
>
> I used =CRYPTKEY= instead of CRYPTKEY, as it is meant to be written in
> an Org document.

sorry

>> +#+begin_src emacs-lisp
>> +  * totally secret :crypt:
>
> There was a missing comma in front of the headline.

Indentation is not enough!?  Is there a document describing how
to contribute to org-manual.org?


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




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

2018-04-27 Thread Gregor Zattler
Hi org-mode users and developers,

Marco Wahl helped me with this: As always the solution is
already there in org-mode.  Attached you find a patch in
order to document this feature.

>From be08948c331118e2c66b858dc3133d3e44bfff69 Mon Sep 17 00:00:00 2001
From: Gregor Zattler <telegr...@gmx.net>
Date: Fri, 27 Apr 2018 14:17:05 +0200
Subject: [PATCH] doc/org-manual.org: Document CRYPTKEY property

TINYCHANGE
---
 doc/org-manual.org | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index e670c387f..76f061709 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19180,6 +19180,16 @@ Here is a suggestion for Org Crypt settings in Emacs init file:
 ;; # -*- buffer-auto-save-file-name: nil; -*-
 #+end_src
 
+It's possible to use different keys for different headings by
+specifying the respective key as property CRYPTKEY, e.g.:
+
+#+begin_src emacs-lisp
+  * totally secret :crypt:
+:PROPERTIES:
+:CRYPTKEY: 0x0123456789012345678901234567890123456789
+:END:
+#+end_src
+
 Excluding the =crypt= tag from inheritance prevents already encrypted
 text from being encrypted again.
 
-- 
2.11.0



* Gregor Zattler <telegr...@gmx.net> [2018-04-26; 16:09]:
> I use org-crypt for different org files.  Till now I follow the
> documentation and specify the one and only key to use via
> (setq org-crypt-key "0xdeadbeef") for all org files and their
> headings.
>
> Is it possible to specify different keys for different files or
> even better for different headings?

Ciao; Gregor

-- 
 -... --- .-. . -.. ..--.. ...-.-


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

2018-04-26 Thread Gregor Zattler
Dear org-mode users and developers,

I use org-crypt for different org files.  Till now I follow the
documentation and specify the one and only key to use via
(setq org-crypt-key "0xdeadbeef") for all org files and their
headings.

Is it possible to specify different keys for different files or
even better for different headings?


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




Re: [O] Bug: master: "Capture abort: (error Format specifier

2018-04-08 Thread Gregor Zattler
Hi Nicolas,
* Gregor Zattler <telegr...@gmx.net> [2018-04-07; 22:30]:
> * Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-04-03; 22:05]:
>> There is no such thing as a "%I" placeholder. Do you mean "%I"?
>
> Yes, I mean %i, the capital %I in this quote is --as I realize
> now, while typing this email-- an abbrev artefact.[1]  I assume I
> pasted from the X11 selection and the abbrev capitalized it.
>
> In my customizations file all templates have %I.  Sorry for this

arrgs: In my customizations file all templates have %i
 ^
> very special noise: this capital I
in my email
> does not explain the capture
> errors I experience with recent git master, since they are not
> part of my templates.

OK, it was a typo in emails, not in the configuration.



I investigated further.  Long story short: My
org-structure-template-alist interfered with capturing.  I
deleted this customisation and capturing works again with org
from git master.




With this minimal .emacs:
(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(org-capture-templates
   (quote
(("t" "test" entry
  (file+olp "~/.notes.org" "test")
  "* %? %^{}G
%i
%^{wann fällig?}T
%a:  notiert am/um: %U")
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )

I was *not* able to trigger the error with org-mode as of git
master.  Therefore the problem has to do with other parts of my
customization. 

Then I turned on debug-on-error and produced a backtrace (see
below).  This is way above my elisp skills, but I realize
something about org-tempo on top of the backtrace.  I have this
module enabled in my customization.  Therefore I disabled it in
org-modules and tested again.  Tada! disabling org-tempo "fixes"
the error.

I the enhanced my minimal .emacs and enabled org-tempo:

(custom-set-variables
 ;; custom-set-variables was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(org-capture-templates
   (quote
(("t" "test" entry
  (file+olp "~/.notes.org" "test")
  "* %? %^{}G
%i
%^{wann fällig?}T
%a:  notiert am/um: %U"
 '(org-modules
   (quote
(org-bbdb org-bibtex org-docview org-gnus org-info org-irc org-mhe 
org-rmail org-tempo org-w3m
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 )


But I was not able to produce the error with org-tempo enabled.

Digging further I discovered org-structure-template-alist which
was configured:

 '(org-structure-template-alist
   (quote
(("s" "#+BEGIN_SRC ?

#+END_SRC")
 ("E" "#+begin_src emacs-lisp ?

#+end_src")
 ("e" "#+BEGIN_EXAMPLE
?
#+END_EXAMPLE")
 ("q" "#+BEGIN_QUOTE
?
#+END_QUOTE")
 ("v" "#+BEGIN_VERSE
?
#+END_VERSE")
 ("V" "#+BEGIN_VERBATIM
?
#+END_VERBATIM")
 ("c" "#+BEGIN_CENTER
?
#+END_CENTER")
 ("l" "#+BEGIN_EXPORT latex
?
#+END_EXPORT")
 ("L" "#+LaTeX: ")
 ("h" "#+BEGIN_EXPORT html
?
#+END_EXPORT")
 ("H" "#+HTML: ")
 ("a" "#+BEGIN_EXPORT ascii
?
#+END_EXPORT")
 ("A" "#+ASCII: ")
 ("i" "#+INDEX: ?")
 ("I" "#+INCLUDE: %file ?")
 ("u" "(use-package ?
;; :ensure nil
;; :commands
;; :bind
;; :init
;; :config
)"

I erased this customization and bingo: capturing works again.
Somehow tempo templates interfere with org capture.

Some day I will customize org-structure-template-alist again,
since templates for use-package and emacs lisp src blocks come in
handy.

Have a nice day, Gregor

Debugger entered--Lisp error: (error "Format specifier doesn’t match argument 
type")
  format("<%c" "s")
  (closure (t) (pair) (format "<%c" (car pair)))(("s" "#+BEGIN_SRC 
?\n\n#+END_SRC"))
  mapcar((closure (t) (pair) (format "<%c" (car pair))) (("s" "#+BEGIN_SRC 
?\n\n#+END_SRC"

Re: [O] Bug: master: "Capture abort: (error Format specifier doesn’t match argument type)"

2018-04-07 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-04-03; 22:05]:
> Gregor Zattler <telegr...@gmx.net> writes:
>
>> Yes, sure.  Sorry, for my laziness.  None of my templates work any more
>> with git master.  This is a (for privacy reasons) shortend version of
>> my customizations, done with the customize system:
>>
>> ...
>>  '(org-capture-templates
>>(quote
>> (("c" "Computer" entry
>>   (file+olp "~/org/grfz.org" "Computer")
>>   "* TODO %? %^{}G
>>   %I
>
> There is no such thing as a "%I" placeholder. Do you mean "%I"?

Yes, I mean %i, the capital %I in this quote is --as I realize
now, while typing this email-- an abbrev artefact.[1]  I assume I
pasted from the X11 selection and the abbrev capitalized it.

In my customizations file all templates have %I.  Sorry for this
very special noise: this capital I does not explain the capture
errors I experience with recent git master, since they are not
part of my templates.

Ciao; Gregor

[1] English is a foreign language to me, I always type the
personal pronoun "I" with a small letter and once thought it
would be a good idea to automatically correct this.  Later I
forgot about this.




Re: [O] Bug: master: "Capture abort: (error Format specifier doesn’t match argument type)"

2018-04-05 Thread Gregor Zattler
Hi Nicolas, org-mode devs,
* Gregor Zattler <telegr...@gmx.net> [2018-04-02; 14:33]:
[...]
> I get
>
> "Capture abort: (error Format specifier doesn’t match argument
> type)"
>
> after hitting the template key in order to capture something.
[...]
> I tried to bisect this with
> make autoloads ; emacs-snapshot -nw --debug-init --eval '(org-capture 4 "t")'
> as a test, but did not find the culprit.

This is, because the bisecting does not find the first bad commit,
but perhaps this helps somehow:

0 (master=) grfz@len:~/src/org-mode$ git bisect start
0 (master|BISECTING=) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf * ; 
git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
Your branch is up-to-date with 'origin/master'.
0 (master|BISECTING=) grfz@len:~/src/org-mode$ git bisect bad
0 (master|BISECTING=) grfz@len:~/src/org-mode$ git co -f 
2348d1834351b57d5ff9bbdb2c74c3e69ed60cfb
Note: checking out '2348d1834351b57d5ff9bbdb2c74c3e69ed60cfb'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  
  git checkout -b 

HEAD is now at 2348d1834... Merge branch 'maint'
0 ((2348d1834...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((2348d1834...)|BISECTING) grfz@len:~/src/org-mode$ git bisect good
Bisecting: 843 revisions left to test after this (roughly 10 steps)
[b6c5a174da7523864d82f6d91cce272d38c1dc95] org-agenda: Refactor 
org-agenda-overriding-header code
0 ((b6c5a174d...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((b6c5a174d...)|BISECTING) grfz@len:~/src/org-mode$ git bisect good
Bisecting: 421 revisions left to test after this (roughly 9 steps)
[ef2485e7ce6e5ef4e47c42898d9bb1b956142df5] manual: Sync with org.texi
0 ((ef2485e7c...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((ef2485e7c...)|BISECTING) grfz@len:~/src/org-mode$ git bisect bad
Bisecting: 210 revisions left to test after this (roughly 8 steps)
[36578fda469b1f5cc48f05c5e07e4aba8c5ae7cb] Merge branch 'maint'
0 ((36578fda4...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((36578fda4...)|BISECTING) grfz@len:~/src/org-mode$ git bisect good
Bisecting: 104 revisions left to test after this (roughly 7 steps)
[a0e3f1d5050ffd0d03c68b35b2b5300fb89da1f0] Merge branch 'maint'
0 ((a0e3f1d50...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((a0e3f1d50...)|BISECTING) grfz@len:~/src/org-mode$ git bisect good
Bisecting: 52 revisions left to test after this (roughly 6 steps)
[9bbee7d3c883efac7c738c6ef66b476d2696fc9a] Add some `:safe' keywords
0 ((9bbee7d3c...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((9bbee7d3c...)|BISECTING) grfz@len:~/src/org-mode$ git bisect bad
Bisecting: 25 revisions left to test after this (roughly 5 steps)
[f8849e92e58fefc9fbea72f650cef50a5607f305] org-archive: Add a test
0 ((f8849e92e...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((f8849e92e...)|BISECTING) grfz@len:~/src/org-mode$ git bisect bad
Bisecting: 12 revisions left to test after this (roughly 4 steps)
[d435c75f543cce08b578a399c531a28c37a48b39] Merge branch 'maint'
0 ((d435c75f5...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  "t")'
0 ((d435c75f5...)|BISECTING) grfz@len:~/src/org-mode$ git bisect good
Bisecting: 6 revisions left to test after this (roughly 3 steps)
[6f89177ee6f7fb5f52f10a54ae10846c803366c5] Move `org-unlogged-message' to 
"org-macs.el"
0 ((6f89177ee...)|BISECTING) grfz@len:~/src/org-mode$ cd ~/src/org-mode; rm -rf 
* ; git co -f ; make autoloads > /dev/null 2> /dev/null; emacs-snapshot  --eval 
'(org-capture 4  &quo

Re: [O] Bug: master: "Capture abort: (error Format specifier doesn’t match argument type)"

2018-04-03 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [2018-04-03; 10:26]:
> Gregor Zattler <telegr...@gmx.net> writes:
>> GNU Emacs 26.0.91 (build 2, x86_64-pc-linux-gnu, GTK+ Version
>> 3.22.11) of 2018-04-02
>> and 
>> Org mode version 9.1.9 (release_9.1.9-560-gf93aa7 @
>> /home/grfz/src/org-mode/lisp/)
>>
>>
>> I get
>>
>> "Capture abort: (error Format specifier doesn’t match argument
>> type)"
>>
>> after hitting the template key in order to capture something.
>
> I cannot reproduce it with default template. Do you use a special one?

Yes, sure.  Sorry, for my laziness.  None of my templates work any more
with git master.  This is a (for privacy reasons) shortend version of
my customizations, done with the customize system:

...
 '(org-capture-templates
   (quote
(("c" "Computer" entry
  (file+olp "~/org/grfz.org" "Computer")
  "* TODO %? %^{}G
  %I
  %^{wann fällig?}T
  %a:  notiert am/um: %U")
 ("e" "Emacs" entry
  (file+olp "~/org/grfz.org" "Computer" "Emacs")
  "* TODO %? %^{}G
  %I
  %^{wann fällig?}T
  %a:  notiert am/um: %U")
 ("o" "Emacs org-mode" entry
  (file+olp "~/org/grfz.org" "Computer" "Emacs" "org-mode")
  "* TODO %? %^{}G
  %I
  %^{wann fällig?}T
  %a:  notiert am/um: %U")
 ("d" "diary the org-mode way" entry
  (file+headline "~/org/diary.org" "aktuell")
  "*** %? %^g
%I
%^{wann fällig?}T
%a:  notiert am/um: %U")
 ("j" "Journal Entry" entry
  (file+olp+datetree "~/org/grfz.org")
  "* %? %^{}G
  %I
  %^{wann fällig?}T
  %a:  notiert am/um: %U")
 ("t" "Todo Entry" entry
  (file+olp "~/org/grfz.org" "Sonstiges")
  "* %? %^{}G
  %I
  %^{wann fällig?}T
  %a:  notiert am/um: %U"
...

Thanks for looking into this, Gregor





[O] Bug: master: "Capture abort: (error Format specifier doesn’t match argument type)"

2018-04-02 Thread Gregor Zattler
Hi org-mode developers,

with

GNU Emacs 26.0.91 (build 2, x86_64-pc-linux-gnu, GTK+ Version
3.22.11) of 2018-04-02

and 

Org mode version 9.1.9 (release_9.1.9-560-gf93aa7 @
/home/grfz/src/org-mode/lisp/)


I get

"Capture abort: (error Format specifier doesn’t match argument
type)"

after hitting the template key in order to capture something.

This is not the case in

Org mode version 9.1.9 (release_9.1.9-3-gb1a639 @
/home/grfz/src/org-mode/lisp/)
from maint as of b1a6395dfeadd9adc5ce7633f341dfbbb30bd39e.


I tried to bisect this with
make autoloads ; emacs-snapshot -nw --debug-init --eval '(org-capture 4 "t")'
as a test, but did not find the culprit.

As a workaround I switched to main.

Thanks for your attention, Gregor




[O] wish: facility to wash org link descriptions

2018-03-02 Thread Gregor Zattler
Hi org-mode developers,

it would be nice if there was a facility to wash (= shorten) org
link descriptions.  From the users perspective this could be a
list of regular expressions with corresponding short forms.

Use case:

I want to automatically shorten org link descriptions,
especially if linking to emails.  Some of this emails are from a
request tracker and have extraordinary long From: and Subject:
suffixes which add up to 49 characters in the link description.
I would like to radically shorten this boilerplate.

Even with "normal" To: and Subject:, the default formatting of
such links prefixes the correspondents name with "from " or "to ".
While it's fine with me to distinguish emails from me from
emails to emails to me, I would not need the "from ").


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




[O] wish: global C-u org-agenda-refile

2017-11-13 Thread Gregor Zattler
Dear org-mode users and developers, I frequently use C-u C-c C-w
in order to jump to a heading in one of my org agenda files
(using helm as a selection framework).

Alas this only works when invoked from org-mode buffers or from
the agenda if point is on an org agenda item (as opposed e.g. to
a line containing the date, or empty time grid lines).

I wish for C-u org-refile functionality (call it org-jump or
whatever) which would not depend on context, in order for me
being able to bind it to a key in the global key map.

Is this already doable?  Otherwise I wish for this
functionality. 

(org-jump works only within an org-mode buffer;
helm-org-agenda-files-headings is an external package and it's
slower than C-u org-refile from cache).


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




Re: [O] org-meta-return not on M-RET

2017-09-16 Thread Gregor Zattler
Hi Nicolas, Allen,
* Nicolas Goaziou  [2017-09-16; 17:20]:
> Allen Li  writes:
>
>> When I could not get org-meta-return to work in terminal Emacs, I
>> realized that org-meta-return is only bound to M-return and not M-RET.
>> Is there any particular reason for this?
>
> No idea. Fixed. Thank you.

Thanks to both of you: It used to work, then it didn't, only a
few days ago I realised there was a difference between M-RETURN
and M-RET but thought of this as a configuration error and now it
simply works again!

Regards, Gregor




Re: [O] is there an easier way to insert an internal link?

2017-08-24 Thread Gregor Zattler
Hi John, org-moders,
* John Kitchin  [2017-08-24; 06:41]:
> I don't think this is in org-mode, but something like
> helm-org-in-buffer-headings has an action for doing something like that.

Yupp, it's on "C-c l" and asks for the description.

Thanks a lot, Gregor




[O] is there an easier way to insert an internal link?

2017-08-24 Thread Gregor Zattler
Der org-mode users,

I'm in a big org-mode file and want to insert a link to a
specific heading.

Till now I go to that heading, do org-store-link,
go back to the insert location and do org-insert-link.

Isnt' there a way to say insert-internal-link-here,
get a list of headings like refile targets, select one
(optionally change link text) and be done?

I do not want to move point in order to insert an
internal link.


I'm sure such facility already exists and I'm blind...

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




Re: [O] Git repository error

2017-05-26 Thread Gregor Zattler
Hi org-mode developers,
* claude fuhrer  [2017-05-26; 09:39]:
> On 26/05/17 01:10, Vicente Vera wrote:
>> Hi. For a while i've been getting this error upon running 'make up0'
>> from my local Org repository:
>>
>> fatal: read error: Connection reset by peer
> I have the same error for every pull, fetch or clone operation. I don't 
> think that it is a problem with my network connection since I can easily 
> sync other project on github.What have I done wrong ?

me too, while at the sane time I see several commits every day
via http://orgmode.org/cgit.cgi/org-mode.git/log/

My org-mode.git/config seems ok to me:

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = git://orgmode.org/org-mode.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[branch "maint"]
remote = origin
merge = refs/heads/maint



Ciao; Gregor 




[O] location of clocking out notes (was: Re: Release 9.0.5)

2017-02-26 Thread Gregor Zattler
Hi Jorge, Bastien, org-mode developers,
* Jorge Morais Neto  [10. Feb. 2017]:
> On 10 February 2017 at 11:53, Bastien  wrote:
>> Org 9.0.5, a minor bugfix release, is out.
> In Org 9.0.5, clock out notes are again stored below the corresponding
> clock line, restoring the behavior of an earlier release.  There were
> interim releases, up to 9.0.4, that stored the clock out notes /above/
> the clock line.

Is there a consensus now where the clocking out notes should go,
even in future versions?  I am affected from this too and before
I start changing the position of all the clocking out notes I
would like to know where to move them.

> Users should be warned to fix clock out notes taken by
> affected Org releases.  Existing important data following the interim
> convention need to be fixed, transposing each affected clock out note
> with the clock line.  If both conventions are mixed, then, to identify
> which clock line corresponds to each clock out note, either the user
> will need to remember the time period when they used an affected
> release, or remember directly which clock out line corresponds to each
> ambiguous note, or analise the version history of their Org files.  So
> the longer the user takes to address the problem, the greater the
> chance of data loss.  I think this issue is important.
> 
> Could we provide an Elisp function to fix this semi-automatically?

This would be great.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




Re: [O] Parser cache is disabled by default

2017-01-21 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou  [21. Jan. 2017]:
> I decided to disable cache by default for the time being. IOW,
> `org-element-use-cache' is nil.
> 
> Please consider turning it on if you want to help debugging the issue.

Is there an easy to follow receipt what to do in order to help
you debugging?  When Emacs hangs I do pkill -USR2 emacs but then
there is no debug info!?


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




[O] [PATCH] ; * doc/org.texi (Key bindings and useful functions): Beautify table.

2017-01-08 Thread Gregor Zattler
Correctly render table of org-babel key bindings even in info
mode. [tiny change]

Copyright-paperwork-exempt: yes
---
 in
 
http://orgmode.org/manual/Key-bindings-and-useful-functions.html#Key-bindings-and-useful-functions
 there is a table with two key bindings on every line where as in 
 (info "Key bindings an useful functions")) these lines are split
 up so that part of the second key binding is on a separate line:
 
 #+BEGIN_EXAMPLE
Active key bindings in Org mode buffer:
 
 ‘C-c C-v p’   or   ‘C-c C-v  ‘org-babel-previous-src-block’
 C-p’
 ‘C-c C-v n’   or   ‘C-c C-v  ‘org-babel-next-src-block’
 C-n’
 #+END_EXAMPLE
 
 This is how I would expect this lines to look:
 
 #+BEGIN_EXAMPLE
Active key bindings in Org mode buffer:
 
 ‘C-c C-v p’   or   ‘C-c C-v C-p’ ‘org-babel-previous-src-block’
 
 ‘C-c C-v n’   or   ‘C-c C-v C-n’ ‘org-babel-next-src-block’
 #+END_EXAMPLE
 
 
 I consider this to be a bug.  This trivial patch fixes this.

 doc/org.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/org.texi b/doc/org.texi
index 2d153ac25..7772d8b84 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -16716,7 +16716,7 @@ Active key bindings in code blocks:
 
 Active key bindings in Org mode buffer:
 
-@multitable @columnfractions 0.45 0.55
+@multitable @columnfractions 0.5 0.5
 @kindex C-c C-v p
 @kindex C-c C-v C-p
 @item @kbd{C-c C-v p} @ @ @r{or} @ @ @kbd{C-c C-v C-p} @tab 
@code{org-babel-previous-src-block}
-- 
2.11.0




Re: [O] Change visibility for bracket links

2016-10-13 Thread Gregor Zattler
Hi Nicolas, org-mode users and developers,
* Nicolas Goaziou  [13. Okt. 2016]:
> Aaron Ecay  writes:
>> My understanding of the problem is that when link fontification is
>> turned on, it is impossible to tell between the two marked positions
>> when point is in in a link like:
>>
>>  [[http://google.com][Search]]
>> ^  ^
>>
>> My suggestion is that we solve the problem in a different way: by
>> changing the color of the cursor when the text is inside the link.
>> So, the cursor would be the default grey color at the first ^ above,
>> and red at the second ^?  (Of course, the color we use for the cursor
>> in links could be changed by customization).  It looks like such an
>> effect is achievable by combining the cursor-sensor-functions text
>> property with set-cursor-color.
>>
>> WDYT?
> 
> That would only partly solve the problem. Cursor's color would tell you
> where you are, but the dance (e.g., C-a or backward-forward) is still
> needed to effectively move to the other side.

But this is a cursor movment problem then.  How about
org-beginning-of-link, org-end-of-link (this already works with
org-next-link as some kind of a substitute of org-beginning-of-link)?


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




Re: [O] Bug: org-add-note closes log book drawer

2016-07-30 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou  [31. Jul. 2016]:
> Hello,
> 
> nljlistb...@gmail.com (N. Jackson) writes:
> 
> > When org-log-into-drawer is t and the log book drawer is open, using
> > org-add-note closes the log book drawer.
> >
> > I think it would be better if org-add-note left the state (open or
> > closed) of the log book drawer alone.
> >
> > In comparison org-clock-in and org-clock-out do leave the state of the
> > log book drawer alone, which is much more satisfactory.
> 
> I understand the discrepancy problem. 
> 
> However, drawers are meant to remove stuff from view, i.e., their
> contents are, more often than not, hidden. So, `org-clock-in' and
> `org-clock-out' may be wrong in this case.

For me the reasoning is the other way around: "Since drawers are meant
to remove stuff from view, i.e., their contents are, more often than
not, hidden", I'd say if the drawer is open prior to org-add-note
there might be a reason why so and it would ne nice not to interfere
with the users choice.

I open my org files in show-everything view for performance reasons.
I have turned on note taking for many funtions like changing TODO
states an cklockin out, therefore the really big drawer collapses all
the time although I want it to stay open.

Just my 2, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




[O] how to rebuild org agenda while emacs is idle?

2016-02-13 Thread Gregor Zattler
Hi org-mode users and developers,

org-agenda is great but slow, sticky agenda solves this but gets
stale really fast.  I try to refresh my org-agenda while Emacs is
idle like so:

(defun gz/refresh-agenda-when-idle ()
  "Refresh Agenda while idle."
(org-agenda-redo 'all))

(setq gz/idle-agenda-timer (run-with-idle-timer 3 t 
'gz/refresh-agenda-when-idle))

This should refresh my agenda after 3 seconds of idle time.  But
when I change one of my agenda files (and save it), the change
does not occur in the agenda after 9 seconds of idle time
although the echo area shows "Rebuilding agenda buffer...done"

What's wrong with this settings?


If you want to play with this, use this test.org:

(defun gz/refresh-agenda-when-idle ()
  "Refresh Agenda while idle."
(org-agenda-redo 'all))

(setq gz/idle-agenda-timer (run-with-idle-timer 3 t 
'gz/refresh-agenda-when-idle))


; in order to cancel the timer ans start afresh:
(cancel-timer gz/idle-agenda-timer)


* Change this heading and watch the agenda buffer: changing?
<2016-02-13 Sa>--<2036-02-13 Mi>


nd visit it like so:
emacs24 -Q -nw /tmp/nuff.org  --eval '(org-agenda-file-to-front)' --eval 
'(org-agenda "a")'

The problem is the same with emacs25 and org-mode from git as of
today (but with emacs25 you'll have to arrange the windows
yourself).


Ciao, Gregor




Re: [O] Bug: [bisected] note from clocking out is above :LOGBOOK: drawer [8.3.3 (release_8.3.3-469-g2e7716 @ /home/grfz/src/org-mode/lisp/)]

2016-01-20 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [20. Jan. 2016]:
> Gregor Zattler <telegr...@gmx.net> writes:
>> It would be great when notes taken when clocking out would come
>> next to their respective clock lines.
> 
> This is already possible: just make sure notes and clocks are stored at
> the same location (e.g., set `org-log-into-drawer' to t in your ECM).

Actually this keeps all notes in the :LOGBOOK: drawer but notes
taken while clocking out appear above instead of below the clock
line.  I would have to shuffle all existing clock-out-notes above
their respective clock line in order to have consistent
documents.  This is doable.

This way notes taken while clocked in are mixed with the ones
taken when clocking out and are even nearer to the clock line.  But...

> However, by default, they aren't.
>
> I see no reason to force notes taken upon clocking out to be always
> located next to the clock line, as long as you can get that behaviour
> somehow. Thus, I think the documentation could be improved as it sort of
> implies clock notes are always next to the closed clock.
> 
> IIUC, you are suggesting to implement two types of notes, but that never
> was the case in Org, AFAICT. You could, however, use a hook (e.g.,
> `org-clock-out-hook') in order to put data relative to clocks in
> a specific drawer and keep general notes in LOGBOOK at the same time.

... I guess this hook will be run before actually clocking out?
Thus I would change the notes drawer to the clock line drawer,
clock out and set it back again?


Thanks for your help, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




Re: [O] Bug: [bisected] note from clocking out is above :LOGBOOK: drawer [8.3.3 (release_8.3.3-469-g2e7716 @ /home/grfz/src/org-mode/lisp/)]

2016-01-20 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [20. Jan. 2016]:
> Gregor Zattler <telegr...@gmx.net> writes:
>> Notes produced when clocking out with org-log-note-clock-out set
>> will be placed above the clock line instead below the clock line.
>> In my heavily customized sessions the notes show up on the
>> previos line respective to the clock line.  Without
>> customizations (see below) they end up above the :LOGBOOK:
>> drawer.
>>
>> ECM:
>> emacs24 -Q -nw -L /home/grfz/src/org-mode/lisp/ --eval "(require 'org)"  
>> --eval '(setq org-log-note-clock-out t)' /tmp/test.org
>>
>> now add a heading, clock in, clock out, write something as a note,
>> do C-c C-c to finish note taking.  Result:
>>
>> * heading
>>   - note
>>   :LOGBOOK:
>>   CLOCK: [2016-01-19 Di 16:22]--[2016-01-19 Di 16:22] =>  0:00
>>   :END:
> 
> I can reproduce it. However, I don't think it is a bug. It looks like
> the expected default behaviour.
> 
> By default, clocks and notes are not stored at the same location. See
> `org-log-into-drawer' and `org-clock-into-drawer'. So, there's no reason
> to put them together here. 
> 
> Moreover, I cannot see anything in the code that would make "clock
> notes" special in any way. This is basically the same as calling
> `org-add-note' right after clocking out, and, as this function's
> docstring points out:
> 
>   This is done in the same way as adding a state change note.
> 
> OTOH, the manual says
> 
>   See the variable ‘org-log-note-clock-out’ for the possibility to
>   record an additional note together with the clock-out timestamp.
> 
> In particular, the term "together" is ambiguous, as it can indeed be
> understood as "at the same place". However, I doubt the intent is to
> create a new type of note that would purposely ignore global logging
> settings. So I lean towards a documentation bug here.
> 
> WDYT?

Thanks for your explanation.  To me this is not a documentation
bug.  What the documentation describes allows for a helpful
distinction of notes in different contexts which IMHO should not
be conflated: 

I understand that to you all notes are created equal: They
somehow belong to a node.

I think the note taken when clocking out belongs specifically to
its clock line and explains it.  Clocking is for reasons of
measurement of time often in context of accounting.  Such notes
answer to the question ""Why took it so long".  This is different
to notes which are there to remember specific aspects of a tasks.

This was default behaviour when users decided to be asked for a
note taken after clocking out.

 I for instance document my working hours this way and have
 2072 such notes sitting below their corresponding clock
 line.
 
 I have the task of maintaining some complex spreadsheets for
 the accounting department.  My employer want's to know how
 much time I spend on this task.  So I clock this working
 hours.  I want to be able to anser to the question why it
 took so long.
 
 OTHT there are notes regarding the work with these complex
 spreadsheets, e.g. "conditional colouring of cells may lead
 to performance problem when thousands of conditionally
 coloured cells are in use".  This is a note which belongs to
 the Spreadsheets and is not only true for the time interval
 indicated by a clock line.
 
It would be great when notes taken when clocking out would come
next to their respective clock lines.


Thanks for your attention, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




[O] Bug: [bisected] note from clocking out is above :LOGBOOK: drawer [8.3.3 (release_8.3.3-469-g2e7716 @ /home/grfz/src/org-mode/lisp/)]

2016-01-19 Thread Gregor Zattler

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

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

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


Notes produced when clocking out with org-log-note-clock-out set
will be placed above the clock line instead below the clock line.
In my heavily customized sessions the notes show up on the
previos line respective to the clock line.  Without
customizations (see below) they end up above the :LOGBOOK:
drawer.

ECM:
emacs24 -Q -nw -L /home/grfz/src/org-mode/lisp/ --eval "(require 'org)"  --eval 
'(setq org-log-note-clock-out t)' /tmp/test.org

now add a heading, clock in, clock out, write something as a note,
do C-c C-c to finish note taking.  Result:

* heading
  - note
  :LOGBOOK:
  CLOCK: [2016-01-19 Di 16:22]--[2016-01-19 Di 16:22] =>  0:00
  :END:



This is with
Package: Org-mode version 8.3.3 (release_8.3.3-469-g2e7716 @ 
/home/grfz/src/org-mode/lisp/)

Emacs version doesn't matter (tested with
- GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 
2015-10-24 on trouble, modified by Debian
and
- Emacs  : GNU Emacs 25.0.50.15 (x86_64-pc-linux-gnu, GTK+ Version 3.18.6) of 
2016-01-19


I git bisected this:

8ddc7314b801b48dff5c246c0954c67021b145f9 is the first bad commit
commit 8ddc7314b801b48dff5c246c0954c67021b145f9
Author: Nicolas Goaziou 
Date:   Tue Jan 12 21:28:32 2016 +0100

Store notes outside drawers at a correct location

* lisp/org.el (org-log-beginning): Move to an appropriate location even
when `org-log-state-notes-insert-after-drawers' is nil and notes are
not stored within a drawer.

Reported-by: swfl...@flintfam.org (Samuel W. Flint)


:04 04 82c4d500315fa5ea5e4e1968e633bfac078f2e6a 
a4fee4c6e2e140cbba8b3fb16513b269b1f9cfe0 M  lisp


Thanks for your attention, Gregor



Re: [O] org-lint complains about incorrect contents for PROPERTIES drawer in inline task (was: Re: how to use org-lint)

2015-10-16 Thread Gregor Zattler
Hi Nicolas, org-mode developers,

I fixed another org-mode file and there is another strange
behaviour of org-lint:

org-lint complains:
  9846 high  Incorrect contents for PROPERTIES drawer

because of this:

* watermelon watermelon watermelon
  :PROPERTIES:
  :CREATED: <2013-07-10 Mi 16:40>
  :END:
  <2013-07-11 Do>
* END

In order to fix it I recreated this inline task (C-c C-x t) and
its PROPERTIES drawer (C-u M-x org-insert-drawer) and the
specified property (C-c C-x p).  Org-lint complains nonetheless.

What to do?

Ciao; Gregor 


* Gregor Zattler <telegr...@gmx.net> [16. Oct. 2015]:
> org-lint cpmlains:
>  10702 low   Misplaced planning info line
> 
> because of this:
> 
> * DONE  xxx X x X
>   DEADLINE: <2011-11-25 Fr>   CLOSED: [2011-12-17 Sa 21:42]  
>   <2011-11-22 Di>
>   :LOGBOOK:
>   - State "DONE"   from "TODO"   [2011-12-17 Sa 21:42] \\
> erledigt
>   :END:
> * END
> 
> is it right to do so?  I thought planning info lines go right
> below the headline?
> 
> Ciao; Gregor
> 
> P.S.: Regarding the problem described below: org-lint worked with
> Emacs-snapshot -Q, so I bisected my init.el.  Now it works while
> nothing relvant changed with respect to the init.el!?  Strange.
> 
> * Nicolas Goaziou <m...@nicolasgoaziou.fr> [15. Oct. 2015]:
>> Gregor Zattler <telegr...@gmx.net> writes:
>> 
>>> When I do this, nothing happens, there is no buffer *Org lint*.
>> 
>> You may want to debug `org-lint', or probably
>> `org-lint--display-reports' then.
>> 
>>> When I do M-: (org-int) it takes a second or two but there is no
>>> *Org-lint* buffer and only this info in *Messages* (I XXXed personal
>>> info):
>> 
>> In non-interactive mode, `org-lint' spits out reports for further
>> processing, or nil when all lights are green. IOW, this is to be
>> expected.
>> 
>> Regards,
>> 
>> 
> 
> Ciao, Gregor
> -- 
>  -... --- .-. . -.. ..--.. ...-.-
> 
> 

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




[O] org-lint complains about planning info line in inline task (was: Re: how to use org-lint)

2015-10-16 Thread Gregor Zattler
Hi Nicolas, org-mode developers,

org-lint cpmlains:
 10702 low   Misplaced planning info line

because of this:

* DONE  xxx X x X
  DEADLINE: <2011-11-25 Fr>   CLOSED: [2011-12-17 Sa 21:42]  
  <2011-11-22 Di>
  :LOGBOOK:
  - State "DONE"   from "TODO"   [2011-12-17 Sa 21:42] \\
erledigt
  :END:
* END

is it right to do so?  I thought planning info lines go right
below the headline?

Ciao; Gregor

P.S.: Regarding the problem described below: org-lint worked with
Emacs-snapshot -Q, so I bisected my init.el.  Now it works while
nothing relvant changed with respect to the init.el!?  Strange.

* Nicolas Goaziou <m...@nicolasgoaziou.fr> [15. Oct. 2015]:
> Gregor Zattler <telegr...@gmx.net> writes:
> 
>> When I do this, nothing happens, there is no buffer *Org lint*.
> 
> You may want to debug `org-lint', or probably
> `org-lint--display-reports' then.
> 
>> When I do M-: (org-int) it takes a second or two but there is no
>> *Org-lint* buffer and only this info in *Messages* (I XXXed personal
>> info):
> 
> In non-interactive mode, `org-lint' spits out reports for further
> processing, or nil when all lights are green. IOW, this is to be
> expected.
> 
> Regards,
> 
> 

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




[O] fix confirmed (was: Re: org-lint complains about incorrect contents for PROPERTIES drawer in inline task)

2015-10-16 Thread Gregor Zattler
Hi Nicolas,

thanks, confirmed for both problems.

Thank you for your fast fix.

Empty *org-lint* buffers give a feeling of security :-)

Ciao; Gregor 

* Nicolas Goaziou <m...@nicolasgoaziou.fr> [16. Oct. 2015]:
> Gregor Zattler <telegr...@gmx.net> writes:
> 
>> I fixed another org-mode file and there is another strange
>> behaviour of org-lint:
>>
>> org-lint complains:
>>   9846 high  Incorrect contents for PROPERTIES drawer
>>
>> because of this:
>>
>> * watermelon watermelon watermelon
>>   :PROPERTIES:
>>   :CREATED: <2013-07-10 Mi 16:40>
>>   :END:
>>   <2013-07-11 Do>
>> * END
>>
>> In order to fix it I recreated this inline task (C-c C-x t) and
>> its PROPERTIES drawer (C-u M-x org-insert-drawer) and the
>> specified property (C-c C-x p).  Org-lint complains nonetheless.
> 
> It should also be fixed along with the previous bug. Thank you.
> 
> Regards,
> 
> -- 
> Nicolas Goaziou
> 
> 

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




[O] how to use org-lint

2015-10-14 Thread Gregor Zattler
Dear org-mode users and developers,

when I do M-x org-lint while the active cpoint is in a org-mode
buffer nothing happens.

When I do M-: (org-lint) I get for instance;

((1 ["118" "high" "Incorrect location for PROPERTIES drawer" 
[cl-struct-org-lint-checker obsolete-properties-drawer "Report obsolete syntax 
for properties drawers" ... high]]) (2 ["922" "high" "Duplicate footnote 
definition \"1\"" [cl-struct-org-lint-checker duplicate-footnote-definition 
"Report duplicate footnote definitions" ... high]]) (3 ["1018" "high" 
"Incorrect location for PROPERTIES drawer" [cl-struct-org-lint-checker 
obsolete-properties-drawer "Report obsolete syntax for properties drawers" ... 
high]]) (4 ["1144" "low" "Misplaced planning info line" 
[cl-struct-org-lint-checker misplaced-planning-info "Report misplaced planning 
info line" ... low]]) (5 ["1257" "high" "Missing definition for footnote 
[fn:BMG]" [cl-struct-org-lint-checker undefined-footnote-reference "Report 
missing definition for footnote references" ... high]]) (6 ["1257" "high" 
"Missing definition for footnote [fn:AGHF]" [cl-struct-org-lint-checker 
undefined-footnote-reference "Report missing definition for footnote 
references" ... high]]) (7 ["1257" "high" "Missing definition for footnote 
[fn:AGHF]" [cl-struct-org-lint-checker undefined-footnote-reference "Report 
missing definition for footnote references" ... high]]) (8 ["1257" "high" 
"Missing definition for footnote [fn:AGHF]" [cl-struct-org-lint-checker 
undefined-footnote-reference "Report missing definition for footnote 
references" ... high]]) (9 ["1264" "high" "Missing definition for footnote 
[fn:BMG]" [cl-struct-org-lint-checker undefined-footnote-reference "Report 
missing definition for footnote references" ... high]]) (10 ["1268" "high" 
"Missing definition for footnote [fn:AGHF]" [cl-struct-org-lint-checker 
undefined-footnote-reference "Report missing definition for footnote 
references" ... high]]) (11 ["5201" "high" "Incorrect location for PROPERTIES 
drawer" [cl-struct-org-lint-checker obsolete-properties-drawer "Report obsolete 
syntax for properties drawers" ... high]]) (12 ["5220" "high" "Incorrect 
location for PROPERTIES drawer" [cl-struct-org-lint-checker 
obsolete-properties-drawer "Report obsolete syntax for properties drawers" ... 
high]]) ...)

in the *Message*  Buffer.

How do I interpret this message?  I would like to fix my org-mode
files but do not know how to with this messages.

I remember vaguely that thee used to be a nicely formatted
results buffer?  

This is on
GNU Emacs 25.0.50.2 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-10-14
Org-mode version 8.3.2 (release_8.3.2-175-gfa61cb 
@/home/grfz/src/org-mode/lisp/)

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




Re: [O] how to use org-lint

2015-10-14 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou <m...@nicolasgoaziou.fr> [14. Oct. 2015]:
> Gregor Zattler <telegr...@gmx.net> writes:
> 
>> when I do M-x org-lint while the active cpoint is in a org-mode
>> buffer nothing happens.
> 
> M-x org-lint should create an "*Org lint*" buffer somewhere. Maybe it is
> buried or on another frame.

When I do this, nothing happens, there is no buffer *Org lint*.

When I do M-: (org-int) it takes a second or two but there is no
*Org-lint* buffer and only this info in *Messages* (I XXXed personal info):


Debug (ox-odt): Searching for OpenDocument styles files...
Debug (ox-odt): Trying /usr/share/emacs/etc/org/styles/... [2 times]
Debug (ox-odt): Trying /home/grfz/src/etc/styles/...
Debug (ox-odt): Trying /home/grfz/src/org-mode/lisp/etc/styles/...
Debug (ox-odt): Trying 
/usr/local/stow/emacs-snapshot/share/emacs/25.0.50/etc/org/...
Debug (ox-odt): Using styles under 
/usr/local/stow/emacs-snapshot/share/emacs/25.0.50/etc/org/
Debug (ox-odt): Searching for OpenDocument schema files...
Debug (ox-odt): Trying /usr/share/emacs/etc/org/schema/... [2 times]
Debug (ox-odt): No OpenDocument schema files installed
((1 ["2395" "low" "Possible incomplete block \"#+BEGIN: clocktable  :tstart 
\"2015-01-01\" :tend \"\" :narrow 80! :minlevel 2 :maxlevel 14 :scope 
agenda :tags \"job\" :stepskip0 :fileskip0 :link :indent\"" 
[cl-struct-org-lint-checker invalid-block "Report invalid blocks" ... low]]) (2 
["2440" "low" "Invalid block closing line \"#+END: clocktable\"" 
[cl-struct-org-lint-checker invalid-block "Report invalid blocks" ... low]]) (3 
["2459" "low" "Misplaced planning info line" [cl-struct-org-lint-checker 
misplaced-planning-info "Report misplaced planning info line" ... low]]) (4 
["2463" "low" "Misplaced planning info line" [cl-struct-org-lint-checker 
misplaced-planning-info "Report misplaced planning info line" ... low]]) (5 
["2545" "low" "Misplaced planning info line" [cl-struct-org-lint-checker 
misplaced-planning-info "Report misplaced planning info line" ... low]]) (6 
["2736" "low" "Misplaced planning info line" [cl-struct-org-lint-checker 
misplaced-planning-info "Report misplaced planning info line" ... low]]) (7 
["3462" "high" "Unknown fuzzy location \" -e \"$envfile\" \"" 
[cl-struct-org-lint-checker invalid-fuzzy-link "Report \"fuzzy\" links with 
unknown destination" ... high]]) (8 ["3570" "high" "Unknown fuzzy location 
\"gitready.com\"" [cl-struct-org-lint-checker invalid-fuzzy-link "Report 
\"fuzzy\" links with unknown destination" ... high]]) (9 ["3589" "low" "Link to 
non-existent local file \"~/src/progit/figures/18333fig0106-tn.png\"" 
[cl-struct-org-lint-checker link-to-local-file "Report links to non-existent 
local files" ... low]]) (10 ["3603" "low" "Link to non-existent local file 
\"~/src/progit/figures/18333fig0201-tn.png\"" [cl-struct-org-lint-checker 
link-to-local-file "Report links to non-existent local files" ... low]]) (11 
["3647" "high" "Unknown fuzzy location 
\"XXX%20XXX%C3%9F%20iXX20%20X%20XXX,%20%20XXX%20XXX,%20%20%0A%20%20XX\""
 [cl-struct-org-lint-checker invalid-fuzzy-link "Report \"fuzzy\" links with 
unknown destination" ... high]]) (12 ["4907" "low" "Misplaced planning info 
line" [cl-struct-org-lint-checker misplaced-planning-info "Report misplaced 
planning info line" ... low]]) ...)


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-




[O] document depreciation of timeline? (was: Re: Bug: Displaying timeline for .org-file and then switching to including inactive timestamps will not include old and future inactive timestamps [8.3.1 (

2015-08-24 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [24. Aug. 2015]:
 There are many advertised limitations to Timeline feature. Actually,
 Timeline feature is moribund[fn:1][fn:2]. Use Agenda view instead.

[... 4 Zeilen gelöscht ...]
 [fn:1] http://thread.gmane.org/gmane.emacs.orgmode/39368/focus=40038
 
 [fn:2] http://permalink.gmane.org/gmane.emacs.orgmode/60518

There are only two commits which mention the timeline in their
summry lines in the newer git history since 2008-01-31.

Shouldn't the feature then be officially depreciated and
mentioned as stale in the manual?  The manual mentions the
timeline in most cases together with the agenda.  And there is a
small chapter dedicated to the timeline.

If depreciation of the timeline is OK I would patch the manual
accordingly. 


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] how to merge two datetrees?

2015-08-23 Thread Gregor Zattler
Hello,

I have two datetrees, each in one org-mode file.  Any ideas how
to merge them?

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] 3 thanks (was: Re: Bug: Capturing to datetree with inactive timestamp messes up level of heading)

2015-08-22 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [22. Aug. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 customizing org to add timestamps in datetrees via …
 (org-datetree-add-timestamp (quote inactive) nil nil Add an
 inactive time stamp when create a datetree entry.)… and
 activating a minimal capture template which captures to a
 datetree results in:

 a)

 * 2015  
 ** 2015-08 August   
 *** 2015-08-19 Mittwoch 
 [2015-08-19 Mi] 
 ** actual entry heading of captured item

 The heading of the newly captured item is at level 2 instead at
 level 4.  I consider this to be a bug.  A second capture item to
 the same day is correctly created at level 4 (and bevor the first
 captured item which does not belong to the same (or any) day in
 the datetree).
 
 Fixed. Thank you.

Thanks.
 2)
 This is a different feature. Since it belongs to the captured entry, the
 timestamp should be defined in your capture template (e.g. %t
 placeholder) instead.

Thanks.
 3)
 See above. You can use %T.

Thanks again.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] Bug: Capturing to datetree with inactive timestamp messes up level of heading

2015-08-20 Thread Gregor Zattler
Dear org-mode developers,

customizing org to add timestamps in datetrees via …
(org-datetree-add-timestamp (quote inactive) nil nil Add an
inactive time stamp when create a datetree entry.)… and
activating a minimal capture template which captures to a
datetree results in:

a)

* 2015  
** 2015-08 August   
*** 2015-08-19 Mittwoch 
[2015-08-19 Mi] 
** actual entry heading of captured item

The heading of the newly captured item is at level 2 instead at
level 4.  I consider this to be a bug.  A second capture item to
the same day is correctly created at level 4 (and bevor the first
captured item which does not belong to the same (or any) day in
the datetree).


2)

The timestamp is added to the heading of the day under which the
captured item is stored iff the day entry is created for this
capture.

I think the timestamp should go with the actual captured entry.
This allows for a timestamp for each captured entry under the
same date heading.  They may be made at different days.


3)

The timestamp adds only a date but I think it’s much more
interesting to capture with date+time.  Think of several journal
entries all done at the same day but at different times of a day.


All three observations werde made with an otherwise uncustimazed
org-mode (emacs -Q).  I created the journal capture template from
the org-capture prompt („C“).


Org-mode version 8.3.1 (release_8.3.1-120-gc5cbc6 @ 
/home/grfz/src/org-mode/lisp/)
GNU Emacs 25.0.50.6 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-08-19 on 
boo


Thanks for your attention, Gregor



[O] how to quote slashes in org-protocol string?

2015-08-16 Thread Gregor Zattler
Dear org-mode users and developers,

how do I quote slashes (/) in TITLE or BODY in org-protocol
string?

 emacsclient org-protocol:/capture:/x/URL/TITLE/BODY

I capture emails from mutt (mail user agent) to org-mode via mutt
macros and bash scripts.  Now I get errors in Emacs „Greedy
org-protocol handler.  Killing client.“ because TITLE (the
Subject of the email) contains slashes.

I tried to quote the slashes with slashes but this chops of part
of the TITLE.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] SOLVED (was: Re: how to quote slashes in org-protocol string?)

2015-08-16 Thread Gregor Zattler
Dear org-mode users and developers,
* Gregor Zattler telegr...@gmx.net [16. Aug. 2015]:
 how do I quote slashes (/) in TITLE or BODY in org-protocol
 string?

Answer: urlencode them as explained in
https://en.wikipedia.org/wiki/Percent-encoding

  emacsclient org-protocol:/capture:/x/URL/TITLE/BODY
 
 I capture emails from mutt (mail user agent) to org-mode via mutt
 macros and bash scripts.  Now I get errors in Emacs „Greedy
 org-protocol handler.  Killing client.“ because TITLE (the
 Subject of the email) contains slashes.
 
 I tried to quote the slashes with slashes but this chops of part
 of the TITLE.

A function to do so in bash can be found at:
http://stackoverflow.com/questions/296536/how-to-urlencode-data-for-curl-command


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] org-lint does not finish on some org-mode buffer

2015-08-09 Thread Gregor Zattler
Dear org-mode developers,

I run org-lint on one of my org-mode buffers -- 13015 lines with
~2000 CLOCK: lines -- and it did not finish within 1 1/2 hours.

Is this a bug?  I did another run for a few minutes and profiled
this on.  Profiler reports are attached.

This is on

GNU Emacs 25.0.50.7 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of
2015-07-29 on boo

and

Org-mode version 8.3.1 (release_8.3.1-16-g2156ab @
/home/grfz/src/org-mode/lisp/)


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-


cpu-profil-on-org-link.gz
Description: application/gzip


memory-profil-on-org-lint.gz
Description: application/gzip


Re: [O] org-lint does not finish on some org-mode buffer

2015-08-09 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [10. Aug. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 I run org-lint on one of my org-mode buffers -- 13015 lines with
 ~2000 CLOCK: lines -- and it did not finish within 1 1/2 hours.

 Is this a bug?  I did another run for a few minutes and profiled
 this on.  Profiler reports are attached.
 
 It looks like an infloop when trying to parse a link. Could you send the
 file, or even bisect the file in order to find problematic link?

You are right.  I bisected the file.  There is a ’’ missing.  At
least with my configuration the attached file ’bad.org’ freezes
Emacs with latest org-mode (but it is in most cases possible to
do a C-G):

emacs-snapshot -Q -L ~/src/org-mode/lisp/  -nw bad.org

I consider this a bug.


File ’good.org’ with closing ’’ does not cause this problems.

Thanks for your help.




Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-
#-*- mode: Org; indent-tabs-mode: nil; coding: utf-8-unix;  -*-

   E-Mail: mailto:abcdef.ab...@abcdef.de
   http://www.ABCDEF.de
   ABCDEF GmbH
#-*- mode: Org; indent-tabs-mode: nil; coding: utf-8-unix;  -*-

   E-Mail: mailto:abcdef.ab...@abcdef.de
   http://www.ABCDEF.de
   ABCDEF GmbH


Re: [O] Why navigating in Org mode is so slow in overview mode?

2015-07-20 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [23. Jun. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 
 These reports are attachet.
 
 Thank you. However, I don't see anything incriminating Org in these
 reports.

Now I think I found something specific.  I do open the org-mode
file in question with #+STARTUP: showeverything because otherwise
it’s slow.  Today I discovered org-goto.  This presents the
buffer in overview mode.  So I started the profiler, started
org-goto and typed 11 letters in order to jump to a heading.
This takes quite some time while my notebooks fan is making noise
and Emacs uses 100% cpu according to htop.

I did this two times with the same org-mode file:

- with Org-mode version 8.3beta (release_8.3beta-1291-gd6e601 @
  /home/grfz/src/org-mode/lisp/) on GNU Emacs 25.0.50.4
  (i686-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-07-17 on boo

- with Org-mode version 8.2.10 (release_8.2.10 @
  /usr/local/stow/emacs-snapshot/share/Emacs/25.0.50/lisp/org/)
  on the same version of Emacs.

I do not know how to read these reports, but to me it seems, that
most of the cpu cycles are used by org-context, org-end-of-item,
org-list-struct and org-list-context.  The memory reports do not
seem to be of interest but I attach them for the sake of
completeness.

HTH, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-


org-goto-profiler-reports.tar.gz
Description: application/gzip


Re: [O] Why navigating in Org mode is so slow in overview mode?

2015-07-20 Thread Gregor Zattler
Hi Nicolas,

thanks for this change it makes a tremendous difference.

* Nicolas Goaziou m...@nicolasgoaziou.fr [20. Jul. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 
 Now I think I found something specific.  I do open the org-mode
 file in question with #+STARTUP: showeverything because otherwise
 it’s slow.  Today I discovered org-goto.  This presents the
 buffer in overview mode.  So I started the profiler, started
 org-goto and typed 11 letters in order to jump to a heading.
 This takes quite some time while my notebooks fan is making noise
 and Emacs uses 100% cpu according to htop.

 I did this two times with the same org-mode file:

 - with Org-mode version 8.3beta (release_8.3beta-1291-gd6e601 @
   /home/grfz/src/org-mode/lisp/) on GNU Emacs 25.0.50.4
   (i686-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-07-17 on boo

 - with Org-mode version 8.2.10 (release_8.2.10 @
   /usr/local/stow/emacs-snapshot/share/Emacs/25.0.50/lisp/org/)
   on the same version of Emacs.

 I do not know how to read these reports, but to me it seems, that
 most of the cpu cycles are used by org-context, org-end-of-item,
 org-list-struct and org-list-context.  The memory reports do not
 seem to be of interest but I attach them for the sake of
 completeness.
 
 I removed a call to `org-context' in
 985420eceb3661aae8b1caafc95e959ab12ad1cb. Does it fix your problem?

Yes, it’s *much* faster now, it’s so responsive it’s almost
instantaneous.  Thanks.

 For the record, `org-context' predates Org Elements and should
 ultimately be removed from the code base.


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] how to have an agenda block as part of an org-mode buffer

2015-07-19 Thread Gregor Zattler
Dear org-moder users and developers,

is it possible to have an agenda block as part of an org-mode
outline?  In my use case I would like to write the minutes of a
meeting and have an autogenerated agenda containing the
dates which are scheduled in other parts of the outline.  Ideally
it would only show dates with a scheduled task but not empty dates.


Something like

* Minutes of the Meeting
** Task 1
*** TODO for Task 1
2015-07-19 So
** Task 2
…
** Agenda of the meeting
#magic agenda Block command
«Agenda with dates from this otline here»
END


Is this doable with org-mode?

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] Why navigating in Org mode is so slow in overview mode?

2015-06-23 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [21. Jun. 2015]:

[Profiler Reports]

 It might not give any useful information. However, the best way to know
 is to look at it.

The first profiler report is after 105 minutes of Emacs uptime.
I had captured infos via org-protocol, refiled them to another
file and then wanted to navigate (arrow keys) to the TODO item in
order to mark it done.  It took seconds till the cursor moved.
Sadly I saved only the memory profiler report.

Then I wrote an reply to your message and while examining the
situation, there was another slow down, when I wanted to switch
buffers via helm, this did nothing for a few secs.  This are the
second reports, only minutes later.

Then I typed ahead and there was a slow down while typing.
System began to swap, emnacs did not respond, I killed Emacs,
firefox, was not able to do a swapoff -a because of memory
restrictions, rebooted the computer, started Emacs with org-mode,
tried to go to the last clocked-in item: and there was a slow
down after say 2 minutes (third profiler reports).

These reports are attachet.

HTH, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-


profiler-report-cpu-2.txt.xz
Description: application/xz


profiler-report-cpu-3.txt.xz
Description: application/xz


profiler-report-mem-3.txt.xz
Description: application/xz


profiler-report.txt.xz
Description: application/xz


profiler-report-mem-2.txt.xz
Description: application/xz


Re: [O] Why navigating in Org mode is so slow in overview mode?

2015-06-21 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [21. Jun. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 - but there some hangs now and then.
 
 Is it a complete freeze (i.e., you need to use C-g to get out of the
 loop) or a slowdown of a couple of seconds? 

It’s a slow down.

 The former is a bug. However, some changes in the buffer imply a massive
 loss of the cache (e.g., inserting a block clears cache in the whole
 section), so the next action can be slow since you need to fill it
 again, hence the slowdown.

Hmh.  Last time I was annoyed was when I wanted the cursor to
move down a few lines in the agenda: pressing „arrow down“ took
two seconds or some such before the cursor actually moved.

 At that moment I cannot
   start the profiler.  If I start the profiler at the
   beginning of using this org file and stop it maybe hours later
   after something was slow: Would such report be helpful?
 
 It might not give any useful information. However, the best way to know
 is to look at it.

OK I’ll start with profiler then.  Thanks, Gregor



Re: [O] Why navigating in Org mode is so slow in overview mode?

2015-06-20 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [17. Jun. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 I would like to help but need help myself on how to produce
 profiler reports.
 
 M-x profiler-start
 
 Do something slow
 
 M-x profiler-report

Thanks, this seemed rather easy and I open the org file in
question in overview now:

- most of the time it’s not slow! That’s great and a big
  difference to months ago, when it was slow very often.

- but there some hangs now and then.  At that moment I cannot
  start the profiler.  If I start the profiler at the
  beginning of using this org file and stop it maybe hours later
  after something was slow: Would such report be helpful? 


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] Why navigating in Org mode is so slow in overview mode?

2015-06-17 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [17. Jun. 2015]:
 Hello,
 
 Q godbles...@gmail.com writes:
 
 I am view this file
 http://doc.norang.ca/org-mode.org

 It's a prettey long document, when it all folded up, navigating to previous
 line and next line takes about 2 seconds. When the sub heading is shown,
 it's more responsive. Is this a bug?
 
 I don't know. What Org version are you using? Could you use a profiler
 and report results?

I thought this is a known problem which gets worse with the
amount of hidden text.  The workaround is to use a
„#+STARTUP: showeverything“ directive.  I use this in order to
make a longish org file with many clocking lines in drawers
usable.

It would be great if this could be fixed.

I would like to help but need help myself on how to produce
profiler reports.  My org mode version is

8.3beta (release_8.3beta-1228-gd1f9aa @ /home/grfz/src/org-mode/lisp/)

but I have this problem since months or years.

Regards, Gregor



Re: [O] Why navigating in Org mode is so slow in overview mode?

2015-06-17 Thread Gregor Zattler
Hi Andreas,
* Andreas Leha andreas.l...@med.uni-goettingen.de [17. Jun. 2015]:
 Shot in the dark: Do have linum-mode enabled?  That is always my first
 candidate when I experience slowdowns.

No I don’t use linum-mode.  Thanks, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] Link-checker for Org-mode

2015-06-02 Thread Gregor Zattler
Hi SabreWolfy,
* SabreWolfy sabrewo...@gmail.com [02. Jun. 2015]:
 Nicolas Goaziou mail at nicolasgoaziou.fr writes:
 
 Org Lint does that already.
 
 Please provide a link. Searching was not helpful.

http://orgmode.org/cgit.cgi/org-mode.git/log/?h=wip-lint

this is to the git repository

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] org-notmuch: how to open-link-at-point in other window?

2015-05-21 Thread Gregor Zattler
Dear org-moders,

I want to open-link-at-point (C-c C-o) in other window.  With
file links this is standard behaviour (at least with my
configuration).  But I don’t know how to do so with notmuch:
links.  Universal argument won’t help.

Any ideas?

I think there should be key bindings for opening in same window,
other window, other frames regardless of the type of link opened.
Is this doable?

How about:

| open in same window  |   C-c C o |
| open in other window | C-c 4 C-c C o |
| open in other frame  | C-c 5 C-c C o |

?

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] org-notmuch: how to open-link-at-point in other window?

2015-05-21 Thread Gregor Zattler
Hi Leo,
* Leo Ufimtsev lufim...@redhat.com [21. May. 2015]:
 I usually use my mouse and right click on the link. 

Thanks, I have problems, emulation right klick with this old
macbook of mine.

 C-c C-o opens things in a new application. E.g a picture is
 opened in my image editing application.
 
 Right clicking opens in the right window. C-u C-c C-o also
 opens images in the right side window.

For the key combos this is not the case with notmuch: -links.  I
don’t knoiw why.


 In emacs, Window and Frame mean something different. By window,
 are you specifically referring to a new plane, split screen
 style, on the right hand side?

Yes.

 As a note, http://emacs.stackexchange.com/ is often a good
 place for questions that have a specific, usually straight
 forward answer.

Thanks, perhaps I give this a try.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] bisected

2015-04-30 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Richard theonewiththeevill...@yahoo.fr [30. Apr. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
  First bad commit is:
  bad0409c3b86e09c4559e97d5f394356c6ccbe7f
 
 Nice hash for a bad commit :) 

I didn't realise :-)

  This results in a startup error:  
  Debugger entered--Lisp error: (void-variable write-back)
 
 Is it related to your initial problem ?

I don't know.  It appeared while git bisecting.

 I think this specific bug was fixed in :
 Commit ea575950d957fcecc74ed6f53c29bb6b77e9fe26

Sorry, no: 
with:
GNU Emacs 25.0.50.6 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of
2015-04-27 on boo Org-mode version 8.3beta (release_8.3beta-1097-gea5759 @ 
/home/grfz/src/org-mode/lisp/)   

and emacs invoked with -Q I cannot save a modified file with ^x ^s
but when I leave emacs:

receipt:
emacs -Q -nw /tmp/tempfile

change buffer, do ^x ^s.

Thanks for looking into this, Gregor



[O] wrong test, fix works, sorry (was: Re: bisected)

2015-04-30 Thread Gregor Zattler
Hi Nicolas,,
* Gregor Zattler telegr...@gmx.net [30. Apr. 2015]:
 * Nicolas Richard theonewiththeevill...@yahoo.fr [30. Apr. 2015]:
  I think this specific bug was fixed in :
  Commit ea575950d957fcecc74ed6f53c29bb6b77e9fe26
 
 Sorry, no: 
 with:
 GNU Emacs 25.0.50.6 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of
 2015-04-27 on boo Org-mode version 8.3beta (release_8.3beta-1097-gea5759 @ 
 /home/grfz/src/org-mode/lisp/)   
 
 and emacs invoked with -Q I cannot save a modified file with ^x ^s
 but when I leave emacs:
 
 receipt:
 emacs -Q -nw /tmp/tempfile
 
 change buffer, do ^x ^s.

I redid my test and now it works...  Probably I forgot the -Q.


Sorry for the noise, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] bisected

2015-04-30 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Richard theonewiththeevill...@yahoo.fr [30. Apr. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
  Sorry, no:
 
 From Bastien's comment, I wonder : does the following patch helps ?

Yes, but see my other email: The fix in
ea575950d957fcecc74ed6f53c29bb6b77e9fe26 works.

Thanks, grgeor




[O] bisected (was: )Re: not in sub-editing buffer

2015-04-30 Thread Gregor Zattler
Hi Daniel, Detlef,
* Detlef Steuer detlef.ste...@gmx.de [30. Apr. 2015]:
 Hi!
 
 On of yesterday's commits introduces an error:
 
 Whatever file I open, I can´t save it with C-c C-s and get the message
 not in sub-editing buffer
 
 I verified org is the culprit using emacs -Q and only loading org.
 
 I can save without/before loading org.


First bad commit is:
bad0409c3b86e09c4559e97d5f394356c6ccbe7f

This results in a startup error:  
Debugger entered--Lisp error: (void-variable write-back)



With 
86dcd907719c97530a266686694a7dc7bd25449a

there is no error.


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] now it get's ridiculous: bug is still there (was: Re: wrong test, fix works, sorry (was: Re: bisected))

2015-04-30 Thread Gregor Zattler
Hi Nicolas, org-mode users and -developers,

I was too much in a hurry...  

This bug still exists as of now:
* Gregor Zattler telegr...@gmx.net [30. Apr. 2015]:
 * Gregor Zattler telegr...@gmx.net [30. Apr. 2015]:
  * Nicolas Richard theonewiththeevill...@yahoo.fr [30. Apr. 2015]:
   I think this specific bug was fixed in :
   Commit ea575950d957fcecc74ed6f53c29bb6b77e9fe26
  
  Sorry, no: 
  with:
  GNU Emacs 25.0.50.6 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of
  2015-04-27 on boo Org-mode version 8.3beta (release_8.3beta-1097-gea5759 @ 
  /home/grfz/src/org-mode/lisp/)   
 
  and emacs invoked with -Q I cannot save a modified file with ^x ^s
  but when I leave emacs:

this is still the case with commit
ea575950d957fcecc74ed6f53c29bb6b77e9fe26 
my mistake was:

  receipt:
  emacs -Q -nw /tmp/tempfile
  
  change buffer, do ^x ^s.

not to load the freshly build org-mode.

With this invocation:

emacs-snapshot -Q -nw -L /home/grfz/src/org-mode/lisp/ --debug-init --eval 
(require 'org) /tmp/testfile

change the buffer, try to save it, see: user-error: Not in a sub-editing 
buffer

This ist the case with:
- GNU Emacs 25.0.50.6 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of
- Emacs24 as of Debian Jessie

it's the caese with org-mode commits up to:

- 14f5b132184ac9c0492d8cc94345413b85ef3f55

- ea575950d957fcecc74ed6f53c29bb6b77e9fe26


it's not the case with org- mode commits up to:

- 86dcd907719c97530a266686694a7dc7bd25449a

- 14f5b132184ac9c0492d8cc94345413b85ef3f55  and patch from Nicolas
  email Message-ID: 87oam56dow@yahoo.fr  appplied.
  But then I get defvar: Symbol's value as variable is void: org-src-mode
  at startup.
  
  
This time I got it right, I hope.

Bye, Gregor



[O] signing of FSF papers needed for documentation changes? (was: Re: PATCH: Document how to scroll calendar by one year at date prompt.)

2015-03-23 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [23. Mar. 2015]:
 I added TINYCHANGE at the end of the commit message, since you don't
 seem to have signed FSF papers. Please correct me if I'm wrong.

You are right.  Thanks.

Do these copyright/assigment issues also apply to documentation
chenges?  One would only be allowed to do max n lines of
documentation changes without legal paperwork with the FSF?

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] PATCH: Document how to scroll calendar by one year at date prompt. (was: Re: Bug: Missing command description in org-mode manual)

2015-03-22 Thread Gregor Zattler
Hi Jens, org-mode developers,
* Haustedt, Jens j.haust...@euroimmun.de [19. Mar. 2015]:
 in the description of the date/time prompt, a section describes the
 control of the calendar from the minibuffer.
 
 There, a description of scrolling the calendar by 1 year is missing. The
 keyboard shortcut is M-S-up/down and works perfectly.

The following patch adds this info to the manual.  It also
justifies the lines to look prettier in info.

Gregor


---
 doc/org.texi | 15 ---
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 6d25df1..49bc562 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6136,13 +6136,14 @@ from the minibuffer:
 @kindex M-S-@key{left}
 @kindex @key{RET}
 @example
-@key{RET}   @r{Choose date at cursor in calendar.}
-mouse-1@r{Select date by clicking on it.}
-S-@key{right}/@key{left} @r{One day forward/backward.}
-S-@key{down}/@key{up} @r{One week forward/backward.}
-M-S-@key{right}/@key{left}   @r{One month forward/backward.}
- /   @r{Scroll calendar forward/backward by one month.}
-M-v / C-v  @r{Scroll calendar forward/backward by 3 months.}
+@key{RET}  @r{Choose date at cursor in calendar.}
+mouse-1@r{Select date by clicking on it.}
+S-@key{right}/@key{left}   @r{One day forward/backward.}
+S-@key{down}/@key{up}  @r{One week forward/backward.}
+M-S-@key{right}/@key{left} @r{One month forward/backward.}
+ /   @r{Scroll calendar forward/backward by one month.}
+M-v / C-v  @r{Scroll calendar forward/backward by 3 months.}
+M-S-@key{down}/@key{up}@r{Scroll calendar forward/backward by one year.}
 @end example
 
 @vindex org-read-date-display-live
-- 
2.1.4


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] PATCH: Document how to scroll calendar by one year at date prompt.

2015-03-22 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [22. Mar. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 * Haustedt, Jens j.haust...@euroimmun.de [19. Mar. 2015]:
 in the description of the date/time prompt, a section describes the
 control of the calendar from the minibuffer.
 
 There, a description of scrolling the calendar by 1 year is missing. The
 keyboard shortcut is M-S-up/down and works perfectly.

 The following patch adds this info to the manual.  It also
 justifies the lines to look prettier in info.
 
 Thank you. 
 
 Could you send it again using git format-patch and add an appropriate
 commit message?

Sure.  In this iteration I also added the respective keys to the
Key index.

Ciao, Gregor
-- 8 --
Subject: [PATCH 1/1] How to scroll calendar by one year at date prompt.

Add respective keys to the Key index.  Also justify the lines in this
block to look prettier in info.
---
 doc/org.texi | 20 
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 
6d25df177d93847dba0f310e6506e5c3c8d2aa40..6b56c4aac6bb802c36a3b076f2ef4bb97019b788
 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6135,14 +6135,18 @@ from the minibuffer:
 @kindex M-S-@key{right}
 @kindex M-S-@key{left}
 @kindex @key{RET}
-@example
-@key{RET}   @r{Choose date at cursor in calendar.}
-mouse-1@r{Select date by clicking on it.}
-S-@key{right}/@key{left} @r{One day forward/backward.}
-S-@key{down}/@key{up} @r{One week forward/backward.}
-M-S-@key{right}/@key{left}   @r{One month forward/backward.}
- /   @r{Scroll calendar forward/backward by one month.}
-M-v / C-v  @r{Scroll calendar forward/backward by 3 months.}
+@kindex M-S-@key{down}
+@kindex M-S-@key{up}
+
+@example
+@key{RET}  @r{Choose date at cursor in calendar.}
+mouse-1@r{Select date by clicking on it.}
+S-@key{right}/@key{left}   @r{One day forward/backward.}
+S-@key{down}/@key{up}  @r{One week forward/backward.}
+M-S-@key{right}/@key{left} @r{One month forward/backward.}
+ /   @r{Scroll calendar forward/backward by one month.}
+M-v / C-v  @r{Scroll calendar forward/backward by 3 months.}
+M-S-@key{down}/@key{up}@r{Scroll calendar forward/backward by one year.}
 @end example
 
 @vindex org-read-date-display-live
-- 
2.1.4






Re: [O] [bug?] org-repair-property-drawers does not repair whole file

2015-03-09 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [08. Mar. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 
 Sadly no: I reapplied `org-repair-property-drawers' on my org
 file with no customisation at all:

 emacs-snapshot -Q -nw -L /home/grfz/src/org-mode/lisp/ file.org 
 ~/src/org-mode/etc/ORG-NEWS

 I loaded `org-repair-property-drawers' from
 ~/src/org-mode/etc/ORG-NEWS and executed it in file.org.  Result
 is ’(nil nil nil nil nil nil nil nil nil nil nil nil ... )’ and
 the buffer file.org remains unmodified.
 
 Doesn't the function fix the anon file you sent?

No.  I removed the line numbers so that the stars of the headings
are at the first column and invoced `org-repair-property-drawers'
in the same way as described above.  The buffer remains
unmodified and the output is `nil'.

 Is it possible to have access to the file? You might want to hide
 contents first with the following function
 
 (defun scramble-contents ()

Yes.  I scrambled it with your function, changed tags (which were
not scrambled by `scramble-contents') and obfuscated clock lines.
The result is attached.

Thanks for looking into this, but if it’s only me: It would be
not much work to clean up the file by hand.

Gregor


scrambled.org.gz
Description: application/gzip


Re: [O] [bug?] org-repair-property-drawers does not repair whole file

2015-03-09 Thread Gregor Zattler
Hi Nicolas, org-mode developers and users,
* Nicolas Goaziou m...@nicolasgoaziou.fr [09. Mar. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 I see invalid property drawers, e.g.,
 
:PROPERTIES:
:Xxxx: Xxx, xx Xxx  xx:xx:xx +
:Xxxx: Xxx Xx x.xxx...@xxx.xx
:Xxx-XX: ....@xxx.xx
:Xxx: XXX XXX - XX xx xx.xx. - Xx xx. xx:xx
:Xx: Xx Xx x.xxx...@xxx.xx, Xxx Xx x.xxx...@xxx.xx, 
 Xx  Xx x.xxx...@xxx.xx, X X x.xx...@xxx.xx, X 
 X  x.xx...@xxx.xx, X Xxxx x.xx...@xxx.xx, X 
 Xxxx  x.x...@xxx.xx, Xxx Xx x.xxx...@xxx.xx, Xxx X 
 Xxxx  x.x...@xxx.xx, Xxxx Xxxx x.xx...@xxx.xx, Xxx X  
 x.xx...@xxx.xx, Xx Xxx x....@xxx.xx, Xxx X  
 x.xx...@xxx.xx, X Xx x....@xxx.xx, Xxx X  
 x.xx...@xxx.xx, Xxxx Xxxx x.x...@xxx.xx, X Xxxx  
 x.x...@xxx.xx
:Xxxx: X XXXxxx,
   xx xx.x. xxx xxx xxx X xxx XXX.

[... 17 lines deleted ...]
   Xxx
:END:
 
 A property drawer can contain only node properties, and there is one
 node property per line.

As you might guess this part represents an email, the multi line
node being the message body.  How would one incorporate such
info in proper org-mode syntax?  Since as of now I do not query
the name=value pairs this is no strict necessity for me.

Is there a syntax checker for org-mode files?

 Ill-formed property drawers were not moved.

Thanks for your explanation and time spent, Gregor



Re: [O] [bug?] org-repair-property-drawers does not repair whole file

2015-03-08 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [08. Mar. 2015]:
 Unfortunately it doesn't ring a bell. 
 
 Running `org-repair-property-drawers' on your file repairs it. Would it
 be related to `org-inlinetask' (i.e., different behaviour if the library
 is loaded or not)?

Sadly no: I reapplied `org-repair-property-drawers' on my org
file with no customisation at all:

emacs-snapshot -Q -nw -L /home/grfz/src/org-mode/lisp/ file.org 
~/src/org-mode/etc/ORG-NEWS

I loaded `org-repair-property-drawers' from
~/src/org-mode/etc/ORG-NEWS and executed it in file.org.  Result
is ’(nil nil nil nil nil nil nil nil nil nil nil nil ... )’ and
the buffer file.org remains unmodified.

This is with:
GNU Emacs 25.0.50.2 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-03-08 on 
boo
Org-mode version 8.3beta (release_8.3beta-893-g1219b0 
@/home/grfz/src/org-mode/lisp/)

I rechecked with emacs24:
GNU Emacs 24.4.91.1 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-03-08 on 
boo
and same org-mode: same result.



Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] [bug?] org-repair-property-drawers does not repair whole file

2015-02-25 Thread Gregor Zattler
Dear org-mode developers, dear Nicolas,

I invoked org-repair-property-drawers on a fairly large org-mode
file.  It did sort some PROPERTIES drawers in front of LOGBOOK
ones but not all.  Since I do not understand the logic of
org-repair-property-drawers I prepared a file with the structure
of the org-mode file after running org-repair-property-drawers on
it:

egrep ^\*+|^ *:PROPERTIES:|^ *:LOGBOOK:|^ *:END: file.org |nl 
headings-properties-logbook-numbered

sed -e s/\(^ 
\+[0-9]\+[[:space:]]*\*\+[[:space:]]*\)\(TODO\|INPROGRESS\|WAITING\|VERIFY\|DONE\|DELEGATED\|CANCELLED\|PUTOFF\|IDEA\)*\(.*$\)/\1\2/
 headings-properties-logbook-numbered headings-properties-logbook-numbered.anon

I don’t how to isolate the bug or the circumstances which trigger
it.  The file headings-properties-logbook-numbered.anon is
attached to this email.  I hope it might be useful to you to find
the bug.

Via

grep -A2 LOGBOOK headings-properties-logbook-numbered.anon|grep PROPERTIES

I can see, that there are 18 occurrences where there is a
PROPERTIES drawer after a LOGBOOK drawer instead before.

Some of the corresponding headings had tags, some not.  And also
some of the not corresponding headings had tags and some not.


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-
 1  * 
 2:PROPERTIES:
 3:END:
 4:LOGBOOK:
 5:END:
 6  *** DONE
 7  :PROPERTIES:
 8  :END:
 9  :LOGBOOK:
10  :END:
11  *** INPROGRESS
12  :LOGBOOK:
13  :END:
14  *** 
15  :LOGBOOK:
16  :END:
17  *** 
18  :LOGBOOK:
19  :END:
20  * DONE
21:LOGBOOK:
22:END:
23  * 
24  *** 
25  :LOGBOOK:
26  :END:
27  * 
28:LOGBOOK:
29:END:
30  * 
31:LOGBOOK:
32:END:
33  *** CANCELLED
34  :LOGBOOK:
35  :END:
36  *** 
37  *** 
38  * DONE
39:LOGBOOK:
40:END:
41  * 
42  * DONE
43  *** TODO
44  :LOGBOOK:
45  :END:
46  *** DONE
47  :LOGBOOK:
48  :END:
49  *** CANCELLED
50  :LOGBOOK:
51  :END:
52  *** DONE
53  :LOGBOOK:
54  :END:
55  * DONE
56:LOGBOOK:
57:END:
58  * DONE
59:LOGBOOK:
60:END:
61  *** PUTOFF
62  :LOGBOOK:
63  :END:
64  *** TODO
65  * 
66  * 
67  * 
68  * 
69  * 
70  * 
71  :LOGBOOK:
72  :END:
73  *** PUTOFF
74  :LOGBOOK:
75  :END:
76  *** DONE
77  *** TODO
78  *** INPROGRESS
79  :LOGBOOK:
80  :END:
81  *** DELEGATED
82  :PROPERTIES:
83  :END:
84  :LOGBOOK:
85  :END:
86  * CANCELLED
87:LOGBOOK:
88:END:
89  * 
90  * 
91  * 
92  * 
93  * 
94  *** INPROGRESS
95  :LOGBOOK:
96  :END:
97  * 
98  * 
99  * DONE
   100:LOGBOOK:
   101:END:
   102  *** INPROGRESS
   103  :LOGBOOK:
   104  :END:
   105  *** CANCELLED
   106  :LOGBOOK:
   107  :END:
   108  *** INPROGRESS
   109  :LOGBOOK:
   110  :END:
   111  * 
   112  * 
   113  * 
   114  * 
   115  *** INPROGRESS
   116  :LOGBOOK:
   117  :END:
   118  * 
   119  *** 
   120  *** 
   121  *** 
   122  *** 
   123  *** 
   124  * 
   125  * 
   126  * 
   127  * 
   128  *** DONE
   129  :LOGBOOK:
   130  :END:
   131  * 
   132  * 
   133  *** 
   134  *** 
   135  * 
   136  *** 
   137  * 
   138:PROPERTIES:
   139:END:
   140  *** 
   141  *** 
   142  *** 
   143  *** 
   144  :PROPERTIES:
   145  :END:
   146  *** 
   147:PROPERTIES:
   148:END:
   149  *** 
   150  * 
   151:PROPERTIES:
   152:END:
   153  * 
   154  * DONE
   155  :LOGBOOK:
   156  :END:
   157  * 
   158:PROPERTIES:
   159:END:
   160  *** DONE
   161  :LOGBOOK:
   162  :END:
   163  :PROPERTIES:
   164  :END:
   165  *** DONE
   166  :LOGBOOK:
   167  :END:
   168  *** DONE
   169  :LOGBOOK:
   170  :END:
   171  *** DONE
   172  :LOGBOOK:
   173  :END:
   174  * 
   175  * 
   176  *** DONE
   177  :LOGBOOK:
   178  :END:
   179  *** DONE
   180  :LOGBOOK:
   181  :END:
   182  *** DONE
   183  :LOGBOOK:
   184  :END:
   185  * 
   186  *** DONE
   187  :LOGBOOK:
   188  :END:
   189  :PROPERTIES:
   190  :END:
   191  *** DONE
   192  :LOGBOOK:
   193  :END:
   194  *** DONE
  

Re: [O] fix is with another glitch when adding two dates

2015-02-06 Thread Gregor Zattler
Hi Nicolas,

I confirm this is fixed.  Thank you very much,
Gregor

* Nicolas Goaziou m...@nicolasgoaziou.fr [05. Feb. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 
 there is still a glitch.  If I now add two items at the same day.:

 rm /tmp/*diary* ; emacs-snapshot -Q -L /home/grfz/src/org-mode/lisp/ -nw 
 --eval '(setq org-agenda-diary-file ??/tmp/diary.org??)'  /tmp/diary.org 
 -f org-agenda
 a
 i
 d
 error1
 i
 d
 error2


 the result is:


 * 2015
 ** 2015-02 Februar
 *** 2015-02-04 Mittwoch
  error2
  2015-02-04 Mi error1
   2015-02-04 Mi

 

 instead of:


 * 2015
 ** 2015-02 Februar
 *** 2015-02-04 Mittwoch
  error2
  2015-02-04 Mi
  error1
  2015-02-04 Mi

 
 
 This should be fixed. Thank you.


-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] fix is with another glitch when adding two dates (was: Re: Bug: org-agenda-diary-entry messes with datetree in org-agenda-diary-file [8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode

2015-02-04 Thread Gregor Zattler
Hi Nicolas, org-mode developers,

there is still a glitch.  If I now add two items at the same day.:

rm /tmp/*diary* ; emacs-snapshot -Q -L /home/grfz/src/org-mode/lisp/ -nw --eval 
'(setq org-agenda-diary-file „/tmp/diary.org“)'  /tmp/diary.org -f org-agenda
a
i
d
error1
i
d
error2


the result is:


* 2015
** 2015-02 Februar
*** 2015-02-04 Mittwoch
 error2
 2015-02-04 Mi error1
  2015-02-04 Mi



instead of:


* 2015
** 2015-02 Februar
*** 2015-02-04 Mittwoch
 error2
 2015-02-04 Mi
 error1
 2015-02-04 Mi




With org-mode as of f9ab1e8ab6b5b6604e838ac992ad51a594ed7130 it’s
correct and „error1“ is above „error2“.  This seems more natural
(at least for me).


I did a git bisect and the first bad commit is Nicolas fix for my
original bug report:
1d4c79d41525113f9e43b82dc9b24d353dc311bd is the first bad commit
commit 1d4c79d41525113f9e43b82dc9b24d353dc311bd
Author: Nicolas Goaziou m...@nicolasgoaziou.fr
Date:   Mon Feb 2 18:19:30 2015 +0100

org-agenda: Fix agenda diary corruption

* lisp/org-agenda.el (org-agenda-insert-diary-make-new-entry): Do not
  save excursion or final position is lost.

Reported-by: Gregor Zattler g...@gmx.de
http://permalink.gmane.org/gmane.emacs.orgmode/94543

:04 04 9226a2e0b05d53fcc633f89663ee9cb6803e2701 
dc0856aa67db029d63f64b9159626468bd93f7f7 M  lisp


Thanks for your attention, gregor

* Gregor Zattler telegr...@gmx.net [03. Feb. 2015]:
 * Nicolas Goaziou m...@nicolasgoaziou.fr [02. Feb. 2015]:
 Gregor Zattler g...@gmx.de writes:
 adding a date to the datetree in the org-agenda-diary-file
 produces a mess:

 - emacs-snapshot -Q -L /home/grfz/src/org-mode/lisp/ -nw –eval (setq 
 org-agenda-diary-file /tmp/diary.org)
 - Mx org-agenda
 - a
 - i
 - d
 - error

 gives:



 * 2015
 ** 2015-02 Februar
 2015-02-01 So*** 2015-02-01 Sonntag
  error

 


 instead of:


 * 2015
 ** 2015-02 Februar
 *** 2015-02-01 Sonntag
  error
 2015-02-01 So
 
 
 This should be fixed. Thank you.
 
 Confirmed, thank you.
 
 Ciao, Gregor
 -- 
  -... --- .-. . -.. ..--.. ...-.-
 

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] Bug: 8.2.10 fails to insert diary entry [as opposed to 8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)]

2015-02-03 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [02. Feb. 2015]:
 Gregor Zattler telegr...@gmx.net writes:
 from the agenda I want to add an entry to the diary.  When I do

 emacs24 -Q -nw
 M-x org-mode
 M-x org-agenda
 a
 i
 d

 I get:

 Diary entry: [d]ay [w]eekly [m]onthly [y]early [a]nniversary [b]lock [c]yclic
 org-agenda-diary-entry: Wrong type argument: commandp,

 and nothing happens.
 
 Could you provide a more complete backtrace, possibly with
 a non-compiled Org (C-u M-x org-reload)?

Sorry, I cannot reproduce it any more.  Which is strange since
nothing changed on this system with respect to this receipt.

Sorry for the noise.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] fix confirmed (was: Re: Bug: org-agenda-diary-entry messes with datetree in org-agenda-diary-file [8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)])

2015-02-03 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Goaziou m...@nicolasgoaziou.fr [02. Feb. 2015]:
 Gregor Zattler g...@gmx.de writes:
 adding a date to the datetree in the org-agenda-diary-file
 produces a mess:

 - emacs-snapshot -Q -L /home/grfz/src/org-mode/lisp/ -nw –eval (setq 
 org-agenda-diary-file /tmp/diary.org)
 - Mx org-agenda
 - a
 - i
 - d
 - error

 gives:



 * 2015
 ** 2015-02 Februar
 2015-02-01 So*** 2015-02-01 Sonntag
  error

 


 instead of:


 * 2015
 ** 2015-02 Februar
 *** 2015-02-01 Sonntag
  error
 2015-02-01 So
 
 
 This should be fixed. Thank you.

Confirmed, thank you.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] Bug: 8.2.10 fails to insert diary entry [as opposed to 8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)]

2015-02-01 Thread Gregor Zattler
Dear org-mode developers,

from the agenda I want to add an entry to the diary.  When I do

emacs24 -Q -nw
M-x org-mode
M-x org-agenda
a
i
d

I get:

Diary entry: [d]ay [w]eekly [m]onthly [y]early [a]nniversary [b]lock [c]yclic
org-agenda-diary-entry: Wrong type argument: commandp,

and nothing happens.


This is 
Org-mode version 8.2.10 (release_8.2.10 @ 
/usr/local/stow/emacs-snapshot/share/emacs/25.0.50/lisp/org/)


This does not happen with version
Org-mode version 8.3beta (release_8.3beta-785-gb5d9f4 @ 
/home/grfz/src/org-mode/lisp/)

HTH, Gregor



[O] Bug: org-agenda-diary-entry messes with datetree in org-agenda-diary-file [8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)]

2015-02-01 Thread Gregor Zattler

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

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

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


Dear org-mode developers,

adding a date to the datetree in the org-agenda-diary-file
produces a mess:

- emacs-snapshot -Q -L /home/grfz/src/org-mode/lisp/ -nw –eval (setq 
org-agenda-diary-file /tmp/diary.org)
- Mx org-agenda
- a
- i
- d
- error

gives:



* 2015
** 2015-02 Februar
2015-02-01 So*** 2015-02-01 Sonntag
 error




instead of:


* 2015
** 2015-02 Februar
*** 2015-02-01 Sonntag
 error
2015-02-01 So


This is with:
Emacs  : GNU Emacs 25.0.50.1 (i686-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2015-02-01 on boo
Package: Org-mode version 8.3beta (release_8.3beta-785-gb5d9f4 @ 
/home/grfz/src/org-mode/lisp/)


I did a git bisect and got:

a1116aa54ee4befd8fa52e3f92207db200ebfd59 is the first bad commit
commit a1116aa54ee4befd8fa52e3f92207db200ebfd59
Author: Nicolas Goaziou m...@nicolasgoaziou.fr
Date:   Fri Jan 30 10:23:47 2015 +0100

Fix ‘org-agenda-insert-diary-make-new-entry’

* lisp/org-agenda.el (org-agenda-insert-diary-make-new-entry): Ensure
point is at a real body line and not in front of meta data, so
regular contents can be inserted safely after a call to this
function.

Reported-by: Samuel Loury konubi...@gmail.com
http://permalink.gmane.org/gmane.emacs.orgmode/94482

:04 04 c02a04761fd8b4f2b518852afca3b44f4f0642ae 
60b6dc4cf3232b8059b8e8c778949d8b466a2e75 M  lisp




Thanks for your attention, Gregor



Re: [O] Stack overflow in regexp matcher

2014-10-24 Thread Gregor Zattler
Hi Charles, org-mode developers
* Charles Berry ccbe...@ucsd.edu [24. Oct. 2014]:
 I do. Try this. Start emacs 24.4.1.
 
 1) Copy this line:
 
 CLOCK: [2013-07-22 Mon 12:29]--[2013-07-22 Mon 15:26] =  2:57
 
 into a new *.org file.
 
 2) Save and close the file and reopen. 
 
 3) If no such error, kill the text in the buffer, and yank it twice.
 
 4) Repeat 2 and 3 till the message
 
File mode specification error: (error Stack overflow in regexp matcher)
 
 shows up. 
 
 5) prune lines from the file and try step 2 till the error disappears.
 
 
 For me somewhere between 400 and 500 lines is the difference between opening
 with no error message and opening with the message.
 
 Emacs 24.3.1 does not show this behavior - no error message. 

I cannot reproduce this.  I even tried with a file with 8264216
such lines.  It took less than 4 minutes to open the file, less
than 24 minutes to recalculate the second to last line.  Then
there was a message in the echo area: Buffer test.org has shrunk
a lot; auto save disabled in that buffer until next real save,
but the buffer was actually as large as before (520645608 bytes).

Mine is
GNU Emacs 24.4.51.1 (i686-pc-linux-gnu, GTK+ Version 3.14.3) of 2014-10-24
and
Org-mode version 8.2.10 (release_8.2.10 @ 
/usr/local/stow/emacs-snapshot/share/emacs/24.4.51/lisp/org/)

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



Re: [O] org agenda clock check shows strange clocking gaps at beginning of day

2014-08-02 Thread Gregor Zattler
Hi Bastien, org developers,
* Bastien b...@gnu.org [27. Jul. 2014]:
 Gregor Zattler telegr...@gmx.net writes:
 
 All three clocking items belong to the same heading.  I'm fine
 with the first clocking gabp.  But why is there a gap of 7536
 minutes shown although ‘org-agenda-clock-consistency-checks’ is
 at default values (gap-around 4:00)?
 
 I've never seen this error -- can you reproduce it consistently?

Yes.  With my org agenda files there are at least two such
errors.  One vanishes with emacs -Q, but not the other.

But both depend on highly private and fairly large org files.
I'll try to reproduce with sharable data but do not have the time
to investigate ATM.  I'll report back when I have something to
share. 

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] org agenda clock check shows strange clocking gaps at beginning of day

2014-07-13 Thread Gregor Zattler
Dear org-mode users and developers,

sometimes clockcheck shows strange clocking gaps:

Sonntag 1 Juni 2014
izt:11:07-11:21 Clocked:   (0:14) heading - description
Clocking gap: 96 minutes
izt:12:57-13:12 Clocked:   (0:15) heading - description
Montag  2 Juni 2014 W23
Dienstag3 Juni 2014
Mittwoch4 Juni 2014
Donnerstag  5 Juni 2014
Freitag 6 Juni 2014
-- Clocking gap: 7536 minutes
izt:18:48-19:00 Clocked:   (0:12) heading - description
Samstag 7 Juni 2014


All three clocking items belong to the same heading.  I'm fine
with the first clocking gabp.  But why is there a gap of 7536
minutes shown although ‘org-agenda-clock-consistency-checks’ is
at default values (gap-around 4:00)?


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file

2014-06-19 Thread Gregor Zattler
Hi Nicolas,
* Nicolas Richard theonewiththeevill...@yahoo.fr [19. Jun. 2014]:
 Gregor Zattler g...@gmx.de writes:
 like so:
 $ cd ~/src/emacs/; rm -rf * ; git co -f emacs-24
 Checking out files: 100% (3525/3525), done.
 Previous HEAD position was 0f0917d... Regenerate AUTHORS and ldefs-boot.el
 Switched to branch 'emacs-24'
 
 (Here I am assuming emacs-24 is still checked out.) 
 
 Could you issue git describe --tags and git branch -a --contains
 HEAD ? I suspect your local emacs-24 branch isn't the actual emacs-24
 branch.
 (OTOH 0f0917d *does* belong to emacs-24, so there's still something
 weird.)

$ cd ~/src/emacs/; rm -rf * ; git co -f emacs-24
Checking out files: 100% (3498/3498), done.
Switched to branch 'emacs-24'
$ git describe --tags
emacs-24.3.91-602-ga92eaac
s$ git branch -a --contains HEAD
* emacs-24
master
remotes/origin/HEAD - origin/master
remotes/origin/master
remotes/origin/trunk


Hmhm.  I have no clue what this signifies.  Perhaps it should
show remotes/origin/master - origin/master?

 cd .git ; cat config
 $ cat config 
 [core]
 repositoryformatversion = 0
 filemode = true
 bare = false
 logallrefupdates = true
 [remote origin]
 url = git://git.savannah.gnu.org/emacs.git
 fetch = +refs/heads/*:refs/remotes/origin/*
 [branch master]
 remote = origin
 merge = refs/heads/master
 
 Shouldn't there be an entry for emacs-24 here ?

I have no clue, but I was suspicious, thats why I pasted this
into my mail.

Thanks for your help.  But if this is only a problem for me, it's
probably easier to wait till emacs officially switches to git and
then clone that repository.

Ciao; Gregor





[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file

2014-06-18 Thread Gregor Zattler
Hi Stefan,
* Stefan Monnier monn...@iro.umontreal.ca [07. Jun. 2014]:
 BTW, I would also point out that people who do not actively develop
 Emacs should ideally use the emacs-24 (i.e. 24.3.9x) branch now rather
 than the trunk (24.4.50), so as to help us fix problems before the
 24.4 release.

I'd love to.  But the emacs-24 branch gives emacs version 24.4.50,
there is a tag emacs-24.3.91 tough, which is from 2014-05-11, whilst
the emacs-24 branch ATM has commits from 2014-06-07.

I'm a novice to version control, but I think a release-branch (as Eli
mentiones in mid:83y4wuth7s@gnu.org) would be great and I think
it's doable with a normal branch!?

Ciao; Gregor





[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file

2014-06-18 Thread Gregor Zattler
Hi Eli,
* Eli Zaretskii e...@gnu.org [18. Jun. 2014]:
  * Stefan Monnier monn...@iro.umontreal.ca [07. Jun. 2014]:
   BTW, I would also point out that people who do not actively develop
   Emacs should ideally use the emacs-24 (i.e. 24.3.9x) branch now rather
   than the trunk (24.4.50), so as to help us fix problems before the
   24.4 release.
  
  I'd love to.  But the emacs-24 branch gives emacs version 24.4.50,
 
 No, the emacs-24 branch's version is 24.3.91.  If you have 24.4.50,
 you've got the trunk there, not the emacs-24 branch.
 
 How did you checkout what you think is the emacs-24 branch?

like so:
$ cd ~/src/emacs/; rm -rf * ; git co -f emacs-24
Checking out files: 100% (3525/3525), done.
Previous HEAD position was 0f0917d... Regenerate AUTHORS and ldefs-boot.el
Switched to branch 'emacs-24'

then I do
$ ./autogen.sh  ./configure  --prefix=/usr/local/stow/emacs-snapshot 
--enable-checking --enable-link-time-optimization --without-toolkit-scroll-bars 
 --with-x-toolkit=gtk3

when I now do (long output ahead)
$ rgrep -- 24\.4\.50
configure.ac:AC_INIT(GNU Emacs, 24.4.50, bug-gnu-em...@gnu.org)
lib/Makefile:PACKAGE_STRING = GNU Emacs 24.4.50
lib/Makefile:PACKAGE_VERSION = 24.4.50
lib/Makefile:VERSION = 24.4.50
lib/Makefile:version = 24.4.50
doc/misc/Makefile:version=24.4.50
doc/lispintro/Makefile:version=24.4.50
doc/lispref/Makefile:version=24.4.50
doc/man/emacs.1:.TH EMACS 1 2007 April 13 GNU Emacs 24.4.50
doc/emacs/Makefile:version=24.4.50
doc/emacs/emacsver.texi:@set EMACSVER 24.4.50
ChangeLog:  * configure.ac: Bump version to 24.4.50.
README:This directory tree holds version 24.4.50 of GNU Emacs, the extensible,
nt/makefile.w32-in:VERSION  = 24.4.50
nt/Makefile:version=24.4.50
nt/config.nt:#define VERSION 24.4.50
configure:# Generated by GNU Autoconf 2.69 for GNU Emacs 24.4.50.
configure:PACKAGE_VERSION='24.4.50'
configure:PACKAGE_STRING='GNU Emacs 24.4.50'
configure:\`configure' configures GNU Emacs 24.4.50 to adapt to many kinds of 
systems.
configure: short | recursive ) echo Configuration of GNU Emacs 24.4.50:;;
configure:GNU Emacs configure 24.4.50
configure:It was created by GNU Emacs $as_me 24.4.50, which was
configure: VERSION='24.4.50'
configure:This file was extended by GNU Emacs $as_me 24.4.50, which was
configure:GNU Emacs config.status 24.4.50
Makefile:version=24.4.50
autom4te.cache/traces.1:m4trace:configure.ac:26: -1- AC_INIT([GNU Emacs], 
[24.4.50], [bug-gnu-em...@gnu.org])
autom4te.cache/output.1:@%:@ Generated by GNU Autoconf 2.69 for GNU Emacs 
24.4.50.
autom4te.cache/output.1:PACKAGE_VERSION='24.4.50'
autom4te.cache/output.1:PACKAGE_STRING='GNU Emacs 24.4.50'
autom4te.cache/output.1:\`configure' configures GNU Emacs 24.4.50 to adapt to 
many kinds of systems.
autom4te.cache/output.1: short | recursive ) echo Configuration of GNU 
Emacs 24.4.50:;;
autom4te.cache/output.1:GNU Emacs configure 24.4.50
autom4te.cache/output.1:It was created by GNU Emacs $as_me 24.4.50, which was
autom4te.cache/output.1: VERSION='24.4.50'
autom4te.cache/output.1:This file was extended by GNU Emacs $as_me 24.4.50, 
which was
autom4te.cache/output.1:GNU Emacs config.status 24.4.50
autom4te.cache/output.2:@%:@ Generated by GNU Autoconf 2.69 for GNU Emacs 
24.4.50.
autom4te.cache/output.2:PACKAGE_VERSION='24.4.50'
autom4te.cache/output.2:PACKAGE_STRING='GNU Emacs 24.4.50'
autom4te.cache/output.2:\`configure' configures GNU Emacs 24.4.50 to adapt to 
many kinds of systems.
autom4te.cache/output.2: short | recursive ) echo Configuration of GNU 
Emacs 24.4.50:;;
autom4te.cache/output.2:GNU Emacs configure 24.4.50
autom4te.cache/output.2:It was created by GNU Emacs $as_me 24.4.50, which was
autom4te.cache/output.2: VERSION='24.4.50'
autom4te.cache/output.2:This file was extended by GNU Emacs $as_me 24.4.50, 
which was
autom4te.cache/output.2:GNU Emacs config.status 24.4.50
autom4te.cache/traces.2:m4trace:configure.ac:26: -1- AC_INIT([GNU Emacs], 
[24.4.50], [bug-gnu-em...@gnu.org])
autom4te.cache/output.0:@%:@ Generated by GNU Autoconf 2.69 for GNU Emacs 
24.4.50.
autom4te.cache/output.0:PACKAGE_VERSION='24.4.50'
autom4te.cache/output.0:PACKAGE_STRING='GNU Emacs 24.4.50'
autom4te.cache/output.0:\`configure' configures GNU Emacs 24.4.50 to adapt to 
many kinds of systems.
autom4te.cache/output.0: short | recursive ) echo Configuration of GNU 
Emacs 24.4.50:;;
autom4te.cache/output.0:GNU Emacs configure 24.4.50
autom4te.cache/output.0:It was created by GNU Emacs $as_me 24.4.50, which was
autom4te.cache/output.0: VERSION='24.4.50'
autom4te.cache/output.0:This file was extended by GNU Emacs $as_me 24.4.50, 
which was
autom4te.cache/output.0:GNU Emacs config.status 24.4.50
lib-src/Makefile:version=24.4.50
msdos/sed2v2.inp:/^#undef VERSION/s/^.*$/#define VERSION 24.4.50/
config.log:It was created by GNU Emacs configure 24.4.50, which was
config.log:| #define PACKAGE_VERSION 24.4.50
config.log:| #define PACKAGE_STRING GNU Emacs 24.4.50
config.log:| #define VERSION 24.4.50

Re: [O] Escaping again!

2014-06-01 Thread Gregor Zattler
Hi Bastien,
* Bastien b...@gnu.org [30. May. 2014]:
[...]
 For now description lists accept both - and +.  I'm all for
 allowing only - so that we could use 
[...]
 in your example.
 
 What do you and others think?

I'd like to be able to use a mix of - or + in list items as to
indicate positive respective negative aspects of something:

* should org-mode support a mix of + and - as the first char in plain 
lists? 
  + would be a great to indicate positive and negative aspects of
something
  - difficult to implement


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-



[O] Bug: creating the agenda gives Arithmetic error [8.2.6 (release_8.2.6-1034-g995808 @ /home/grfz/src/org-mode/lisp/)]

2014-05-24 Thread Gregor Zattler

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

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

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


Dear org-mode developers,

I cannnot create an agenda due to a erroneous stats cookie in a
headline of an org file:


If I do C-c a a emacs opens a *Org Agenda* window but it is
empty and the message Arithmetic Error appears in the echo
line.  In the  *Message* buffer I'm told:

Press key for agenda command:
if: Arithmetic error


I bisected the repo:

45c4f276f266fc41530128e1069979eb8df50fa2 is the first bad commit
commit 45c4f276f266fc41530128e1069979eb8df50fa2
Author: Bastien Guerry b...@altern.org
Date:   Fri May 23 15:54:50 2014 +0200

org.el: Implement agenda sorting against stats cookies.  Code
cleanup


I bisected my org-agenda-files and found a minimal example which
triggers the bug:


*** Some Appointment [0/0]
2013-09-12 Do 19:00
- People [6/11]
  - [X] Alice
  - [X] Bob
  - [X] Mallorey
  - [X] A
  - [ ] B
  - [ ] C
  - [X] D
  - [ ] E
  - [X] F
  - [ ] G
  - [ ] H


Note the wrong stats cookie '[0/0]' in the headline.

I'll remove the '[0/0]' but it woukld be nice if org-mode would
report the erroneous stats cookie instead of throwing an
arithmetic error.


Thanks, Gregor



Emacs  : GNU Emacs 24.4.50.1 (i686-pc-linux-gnu, GTK+ Version 3.12.2)
 of 2014-05-23 on boo
Package: Org-mode version 8.2.6 (release_8.2.6-1034-g995808 @ 
/home/grfz/src/org-mode/lisp/)



  1   2   >