Re: [O] Show weekday in daily agenda view

2019-05-20 Thread Bernt Hansen
db...@attentigroup.com (J. David Boyd) writes:

> Nick Dokos  writes:
>
>> db...@attentigroup.com (J. David Boyd) writes:
>>
>>> Nick Dokos  writes:
>>>
 johanna@th-koeln.de writes:

> maybe I did not search the right way in google alias startpage. But I
> could not figure out how to write next to the date e.g. 2000-04-01 the
> weekday, i.e. the specific day of the week. It would come very handy to
> have the date displayed as 2019-05-14 Tu and 2019-05-15 We and so on. Or
> even have it spelled out as 2019-05-14 Tuesday.
>

 How do you generate that view?

 Doesn't your agenda view already show the day of the week?  With the
 recommended keybinding, I get a daily agenda with C-c a a d.

 Mine starts like this:

 ,
 | Day-agenda (W20):
 | Tuesday14 May 2019
 |8:00.. 
 |   appts:  10:00-11:30 Tools Meeting
 |   10:00.. 
 |   12:00.. 
 |   14:00.. 
 |   16:00.. 
 |   18:00.. 
 |   20:00.. 
 |   work:   Sched.Xx:  TODO Review PR
 |   work:   Sched.2x:  TODO Add issue
 |   Weather:OpenWeatherMap: light rain, 3-8°C, 1010hpa, 90%, 3m/s
 `

 so it definitely shows the weekday, but perhaps you are doing something
 different?
>>>
>>>
>>> How do you generate *that* view?  How do you have it creating sub-groups?  
>>> All
>>> I get is a straight-forward list of days and times, with all items in chrono
>>> order
>>>
>>
>> Not sure what you mean by "sub-groups". And I'm pretty sure I don't do
>> anything special to get this. The grid is the standard grid - I
>> believe that comes "free" with the default settings of
>> org-agenda-time-grid and org-agenda-use-time-grid.
>>
>> The appts:, work: and Weather: thingies are "categories" - the first
>> two come from the name of the agenda file where the item originated:
>> I have a work.org file for work items and an appts.org file which contains 
>> just
>> reminders. It actually contains a bit more: there are top-level headlines
>> for Anniversaries, Weather and Appointments like this:
>>
>> ,
>> | * Anniversaries
>> |:PROPERTIES:
>> |:CATEGORY: Anniv
>> |:ID:   409062f6-6cb1-467f-b192-2dfcb7b384ca
>> |:END:
>> | %%(org-bbdb-anniversaries)
>> | 
>> | * Weather
>> |   :PROPERTIES:
>> |   :CATEGORY: Weather
>> |   :END:
>> | %%(org-weather)
>> | 
>> | * Appointments
>> | ** APPT Doctor appt 
>> | 
>> `
>>
>> Items in the Appoinments section don't have a defined Category
>> so they are labeled with the fill name ("appts"). Anniversaries
>> and Weather items have a CATEGORY property so they are labeled
>> by  the explicit category.
>>
>> I don't remember whether I do anything special to sort the items
>> (e.g. why the Weather item is always last). If you are interested
>> in that, I can dig a little more into my configuration.
>>
>> Does that answer your question?
>
>
> That helps immensely, evidently I have some reading to do, so I understand
> more of how to change the agenda view around.
>
> And yes please, could/would you check your config and see if anything special
> is done?
>
> Thanks very much!
>
> Dave in Hudson, FL

Make sure you have files contributing to org-agenda-files otherwise your
agenda view will be empty.

Regards,
Bernt



Re: [O] Converting tags to TODO states

2019-04-16 Thread Bernt Hansen
garj...@garjola.net writes:

> Hi,
>
> For my GTD implementation with org-mode, I have been using the :next:
> tag for my next actions. I would like now to use a "NEXT" TODO keyword,
> which means that I need to convert all :next: tags with "TODO" headlines
> into "NEXT" headlines without the :next: tag. 
>
> I have *a lot* of org files, so an automatic procedure is needed. Since
> I am not fluent in elisp, I was going to write a python script to do
> this, but maybe there is already a way to do this conversion with
> org-mode itself?
>
> The tricky thing I see with parsing is dealing with the ":" in the case
> of multiple tags (I know how to do this in python, but I don't in
> elisp).
>
> Thanks for any hint you can provide.
>
> Garjola

As this is a one-time change I would just use the agenda and bulk
operations to fix your entries.

If the files already contribute to your agenda (I assume they do) 
you can just run a tag match on :next:

C-c a m next RET

and mark all the entries returned with 

m (repeat for each task)

then add a NEXT todo keyword

B t NEXT RET

and mark all the tasks again

m (repeat for each task)

and remove the :next: tag

B - next RET

and save your files.

HTH,
Bernt



[O] BUG: Capture task clocking doesn't stop due to narrowing

2019-03-16 Thread Bernt Hansen
Hi,

I ran into an issue this morning where my capture task continues
clocking on save.  This occurs in both master and maint when not
clocking into a drawer.

ECM follows.


--- test.org ---
#+TITLE: BUG: Capture with clocking does not stop the clock due to narrowing

*Keys To Reproduce*

1) Capture a new entry
   C-c c w

2) Save entry - clock should stop but doesn't
   C-c C-c

The clock is still running after save but should have been
stopped. The clock was not included in the narrowed buffer in the
capture window.  If we widen the buffer before saving the clock is
stopped normally.

Same results in both maint and master branch.

CLOCK changed to KLOCK in example below to avoid before first headline
error.  The clock line is being picked up even though it is inside an
example block and the clock resolution code is trying to deal with it.

#+begin_example
  ,* Tasks
  ,* Work Log
  ,** DONE Capture bug details
  KLOCK: [2019-03-16 Sat 16:09]
  ,* Personal Log
#+end_example

GNU Emacs 25.1.1 (x86_64-w64-mingw32) of 2016-09-17
Org mode version 9.2.2 (release_9.2.2-312-gce1681 @ 
c:/D-Drive/bin/org-mode/lisp/)

* Tasks
* Work Log
* Personal Log
--- minimal.emacs --
(add-to-list 'load-path "C:/D-Drive/bin/org-mode/lisp/")
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\)$" . org-mode))
(require 'org)

(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cb" 'org-iswitchb)
--- test.el 
(global-set-key (kbd "C-c c") 'org-capture)

;; Save clock data and state changes and notes in the LOGBOOK drawer
(setq org-clock-into-drawer 4)

(setq org-adapt-indentation nil)

(setq org-capture-templates
  (quote (("t" "Todo" entry (file "~/test.org")
   "* TODO %?\n\n%x\n" :clock-in t :clock-resume t)
  ("p" "Personal Log" entry (file+olp "~/test.org" "Personal Log")
   "* DONE %?\n" :clock-in t :clock-resume t)
  ("w" "Work Log" entry (file+olp "~/test.org" "Work Log")
   "* DONE %?\n" :clock-in t :clock-resume t
--- windows icon properties to start minimal emacs -
C:\D-Drive\bin\emacs-25.1\bin\runemacs.exe -q -l ~/minimal.emacs -l ~/test.el 
~/test.org

Regards,
Bernt



Re: [O] Regression - problem with links

2019-03-16 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> Bernt Hansen  writes:
>
>> Here is my ECM:
>
> Fixed. Thank you.
>
> Regards,

Confirmed.  Thanks for the lightning quick response!

I have another issue I will send separately.

Regards,
Bernt



Re: [O] Regression - problem with links

2019-03-16 Thread Bernt Hansen
Bernt Hansen  writes:

> Marco Wahl  writes:
>
>> IOW I can't reproduce your issue AFAICS.
>>
>> Is it a configuration issue?
>
> Possibly.  I will try to produce an ECM for the issue I am seeing.
>
> Regards,
> Bernt

Here is my ECM:

--- test.org ---
Regression - problem with links

*Keys To Reproduce*

1) Move to Update Timekeeper and OTL 2019 headling
   C-c C-n

2) Open links
   C-c C-o

Results in maint branch (0007df863 (org-lint: Do not warn about URL setup 
files, 2019-03-14))
Org mode version 9.2.2 (release_9.2.2-13-g0007df @ 
c:/D-Drive/bin/org-mode/lisp/)
GNU Emacs 25.1.1 (x86_64-w64-mingw32) of 2016-09-17

#+begin_example
[1]  Link One (https://xxx.yyy.zzz)
[2]  Line Two (https://foo.bar.baz)
[3]  Line Three (https://aaa.bbb)
[4]  Link Four (https://ccc.ddd)
[5]  Link Five by id (id:eb1085ed-15fe-46a3-8b5e-3971587d1123)
[6]  Link Six by id (id:11886507-bb77-49fb-af59-9d5ac43dce0d)
#+end_example

Results in master branch (a70ab164f (org-manual: Small fixes, 2019-03-16))
Org mode version 9.2.2 (release_9.2.2-311-ga70ab1 @ 
c:/D-Drive/bin/org-mode/lisp/)
GNU Emacs 25.1.1 (x86_64-w64-mingw32) of 2016-09-17

#+begin_example
[1]  https://xxx.yyy.zzz
[2]  https://foo.bar.baz
[3]  https://aaa.bbb
[4]  https://ccc.ddd
[5]  id:eb1085ed-15fe-46a3-8b5e-3971587d1123
[6]  id:11886507-bb77-49fb-af59-9d5ac43dce0d
#+end_example

* TODO Update Timekeeper and OTL 2019

[[https://xxx.yyy.zzz][Link One]]

[[https://foo.bar.baz][Line Two]]

[[https://aaa.bbb][Line Three]]

[[https://ccc.ddd][Link Four]]

[[id:eb1085ed-15fe-46a3-8b5e-3971587d1123][Link Five by id]]

[[id:11886507-bb77-49fb-af59-9d5ac43dce0d][Link Six by id]]


--- minimal.emacs --
(add-to-list 'load-path "C:/D-Drive/bin/org-mode/lisp/")
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org)

(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cb" 'org-iswitchb)
--- test.el 
; empty file
--- windows icon properties to start minimal emacs -
C:\D-Drive\bin\emacs-25.1\bin\runemacs.exe -q -l ~/minimal.emacs -l ~/test.el 
~/test.org

Regards,
Bernt



Re: [O] Regression - problem with links

2019-03-16 Thread Bernt Hansen
Marco Wahl  writes:

> IOW I can't reproduce your issue AFAICS.
>
> Is it a configuration issue?

Possibly.  I will try to produce an ECM for the issue I am seeing.

Regards,
Bernt



Re: [O] Regression - problem with links

2019-03-15 Thread Bernt Hansen
Bernt Hansen  writes:

> Marco Wahl  writes:
>
>> Hi,
>>
>> [...]
>>
>>> My links are like this:
>>>
>>>
>>> [[https://somewebsiteaddress.net/path/to/page.do][Timekeeper]]
>>> [[id:eb1085ed-15fe-46a3-8b5e-3971587d1123][OTL 2019]]
>>>
>>> and I want to see
>>>
>>> [1] Timekeeper
>>> [2] OTL 2019
>>>
>>> but instead I get the address like this which is much less useable
>>>
>>> [1] https://somewebsiteaddress.net/path/to/page.do
>>> [2] id:eb1085ed-15fe-46a3-8b5e-3971587d1123
>>
>> This sounds like a bug fixed a few days ago.
>>
>> 
>> https://code.orgmode.org/bzg/org-mode/commit/b1429cdfe043b199bb7be6dc5c97a299954b4e0d
>>
>> Can you check if the fix is in your copy of Org?
>
> I have that commit in my current git version.
>
> Last week I noticed agenda clock reports had file: text before this fix
> and reverted back to normal looking clock reports after however the menu
> from C-c C-o doesn't display link descriptions for me.
>
> I'll try to isolate which commit breaks this.
>
> Regards,
> Bernt

My current master  is

f0dc3a06d (test-org-clock: Fix one test, 2019-03-15)

This may be another case that isn't covered by the fix.
maint displays links correctly but master does not for me in the menu
when you select a link to jump to with C-c C-o from the heading or from
the agenda.

git bisect identifies the following commit:

2b00d6281606ef295dadbe4ddd929ebdd6716d60 is the first bad commit
commit 2b00d6281606ef295dadbe4ddd929ebdd6716d60
Author: Nicolas Goaziou 
Date:   Sat Mar 9 10:58:41 2019 +0100

Change bracket link escape syntax

* contrib/lisp/org-link-edit.el (org-link-edit--link-data):
* lisp/ob-tangle.el (org-babel-tangle-comment-links): Update
match-group.
(org-babel-detangle): Remove unnecessary `org-link-escape' call.
(org-babel-tangle-jump-to-org): Update match group.
(org-link-url-hexify):
(org-link-escape-chars): Remove variables.
* lisp/ol.el (org-link--decode-compound): Renamed from
  `org-link--unescape-compound'.
(org-link--decode-single-byte-sequence): Renamed from
`org-link--unescape-single-byte-sequence'.
(org-link-make-regexps): Update `org-link-bracket-re' syntax.
(org-link-encode): New function, renamed from `org-link-escape'.
(org-link-decode): New function, renamed from `org-link-unescape'.
(org-link-escape):
(org-link-unescape): Use new escape syntax.
(org-link-make-string): Apply new escaping rules.
(org-link-display-format):
(org-insert-link): Update match group.
* lisp/org-agenda.el (org-diary):
(org-agenda-format-item):
(org-agenda-to-appt): Update match group.
* lisp/org-clock.el (org-clocktable-write-default): Update match
group.
* lisp/org-element.el (org-element-link-parser): Update match group.
* lisp/org-mobile.el (org-mobile-escape-olp):
(org-mobile-locate-entry): Apply function renaming.
* lisp/org-protocol.el (org-protocol-split-data):
(org-protocol-parse-parameters): Apply function renaming.
* lisp/org.el (org-refile): Update match group.
* testing/README (Interactive testing from within Emacs): Fix
  examples.
* testing/lisp/test-ol.el (test-ol/encode): Merge old escape tests.
(test-ol/decode): Merge old unescape tests.
(test-ol/escape):
(test-ol/unescape):
(test-ol/make-string): New tests.
* testing/lisp/test-org-clock.el (test-org-clock/clocktable/link):
* testing/lisp/test-org.el (test-org/custom-id):
(test-org/fuzzy-links):
* testing/lisp/test-ox.el (test-org-export/resolve-fuzzy-link):
Update
  tests.

:04 04 474dd71a09f6396ef593cf061aa0001968fb5412
976cda41aeecca75da7c5982aeb89a2cde5e5567 M  contrib
:04 04 2ab4f30b6deac5cfc4c9e83fc1f2ac013232f8da
d7b6b3c0ff0adda1a557dfe87bffd0d8f17f6659 M  lisp
:04 04 133b3e5e20e848a7347ca4c73c517bca4120461d
28f9768c483af5bce6a242889360747be4ac865a M  testing

Regards,
Bernt.



Re: [O] Regression - problem with links

2019-03-15 Thread Bernt Hansen
Marco Wahl  writes:

> Hi,
>
> [...]
>
>> My links are like this:
>>
>>
>> [[https://somewebsiteaddress.net/path/to/page.do][Timekeeper]]
>> [[id:eb1085ed-15fe-46a3-8b5e-3971587d1123][OTL 2019]]
>>
>> and I want to see
>>
>> [1] Timekeeper
>> [2] OTL 2019
>>
>> but instead I get the address like this which is much less useable
>>
>> [1] https://somewebsiteaddress.net/path/to/page.do
>> [2] id:eb1085ed-15fe-46a3-8b5e-3971587d1123
>
> This sounds like a bug fixed a few days ago.
>
> 
> https://code.orgmode.org/bzg/org-mode/commit/b1429cdfe043b199bb7be6dc5c97a299954b4e0d
>
> Can you check if the fix is in your copy of Org?

I have that commit in my current git version.

Last week I noticed agenda clock reports had file: text before this fix
and reverted back to normal looking clock reports after however the menu
from C-c C-o doesn't display link descriptions for me.

I'll try to isolate which commit breaks this.

Regards,
Bernt



[O] Regression - problem with links

2019-03-15 Thread Bernt Hansen
Hi,

I have a habit with a list of links in it which I use to navigate to
places for dealing with the task.

Recently C-c C-o shows the link address instead of description which
makes it hard to use.  This occurs for C-c C-o on the headline of the
task and also in the agenda.

My links are like this:


[[https://somewebsiteaddress.net/path/to/page.do][Timekeeper]]

[[id:eb1085ed-15fe-46a3-8b5e-3971587d1123][OTL 2019]]

and I want to see

[1] Timekeeper
[2] OTL 2019

but instead I get the address like this which is much less useable

[1] https://somewebsiteaddress.net/path/to/page.do
[2] id:eb1085ed-15fe-46a3-8b5e-3971587d1123

I have multiple lists with multiple id: entries so I can't tell which is
which anymore from the headline.  My workaround is to display the task
and do C-c C-o on the task I need to visit.

I am on the latest git master commit as of this morning.

Regards,
Bernt



Re: [O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

2019-03-04 Thread Bernt Hansen
Actually I think it is a bug.  This weird behaviour has been around for
a very long time (years probably).

I have noticed similar behaviour with log mode, and clock check mode as
well.

I can reproduce the issue at with the following recipe:

C-c a a (start org agenda)
j -3 RET (go back 3 days although any number of days probably works)
l (turn on log mode) or R for clock report
. (go to today)
l (wont' turn off log mode anymore)

Workaround:

j -3 RET (go back 3 days again)
l (turn log mode off) or R for clock report
.  (works normally again)

I run into this regularly when I'm checking clock reports in the agenda
for the past week (jump to the past, turn clock reports or logging on)
then move forwards again and you can't turn it off.

HTH.

Regards,
Bernt

Daniel Ortmann  writes:

> This is crazy!  After months of problems, I myself no longer can
> reproduce this issue!  :-/
>
> Comments welcome (Please!) ... but this issue no longer is actually a bug. 
>
> On 3/4/19 3:22 PM, Daniel Ortmann wrote:
>> Remember to cover the basics, that is, what you expected to happen and
>> what in fact did happen.  You don't know how to make a good report?  See
>>
>>  
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__orgmode.org_manual_Feedback.html-23Feedback=DwIGaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=Dkq-B4wf3U4UeyggH34kSw8HWPy7CqI3u3RwPXz2f5o=4fSQsyYOysB0leNb80s58m3u_JCrMhGMzVXrgGispfw=_u3sTu0de7IKTb2RsyImTOaTAqX4pl-EiuT_gDXAtXA=
>>
>> Your bug report will be posted to the Org mailing list.
>> 
>>
>> Since this problem has been occurring for a few months now, it's got to
>> be something wrong in my configuration.
>>
>> In the org agenda, pressing R activates the clock report but pressing it
>> again does not turn it off.  The same behavior occurs through the menu;
>> clicking the view clock report checkbox turns the checkbox on and the
>> clock report appears in the agenda ... but clicking it again does not
>> turn the clock report off; it stays visible.
>>
>> To log the bug report I started with
>> emacs -Q -l ~/minimal-org.el
>> then ran M-x org-agenda followed by a and then R.
>> The following debug trace immediately occurred.
>>
>> Please clue in the clueless.
>> Thank you!
>>
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>>   file-exists-p(nil)
>>   org-check-agenda-file(nil)
>>   org-agenda-prepare-buffers((nil))
>>   org-dblock-write:clocktable((:name "clocktable" :link t :maxlevel 2
>> :tstart 737122 :tend 737123 :scope agenda :indentation-column 0 :content
>> "\n"))
>>   org-update-dblock()
>>   org-clock-get-clocktable(:link t :maxlevel 2 :tstart 737122 :tend
>> 737123 :scope agenda)
>>   apply(org-clock-get-clocktable (:link t :maxlevel 2 :tstart 737122
>> :tend 737123 :scope agenda))
>>   org-agenda-list(nil 737122 day nil)
>>   (let nil (org-agenda-list 'nil 737122 'day nil))
>>   eval((let nil (org-agenda-list 'nil 737122 'day nil)))
>>   org-let(nil (org-agenda-list 'nil 737122 'day nil))
>>   org-agenda-redo()
>>   org-agenda-clockreport-mode()
>>   funcall-interactively(org-agenda-clockreport-mode)
>>   call-interactively(org-agenda-clockreport-mode nil nil)
>>   command-execute(org-agenda-clockreport-mode)
>>
>>
>> Emacs  : GNU Emacs 27.0.50 (build 3, x86_64-pc-linux-gnu, X toolkit,
>> Xaw3d scroll bars)
>>  of 2019-03-04
>> Package: Org mode version 9.2.2 (release_9.2.2-245-g9d7b1e @
>> /home/dortmann/src/git-org-mode/lisp/)
>>
>> current state:
>> ==
>> (setq
>>  org-src-mode-hook '(org-src-babel-configure-edit-buffer
>>          org-src-mode-configure-edit-buffer)
>>  org-metadown-hook '(org-babel-pop-to-session-maybe)
>>  org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
>>  org-mode-hook '(#[0 "\300\301\302\303\304$\207"
>>            [add-hook change-major-mode-hook org-show-all append local]
>>            5]
>>          #[0 "\300\301\302\303\304$\207"
>>            [add-hook change-major-mode-hook org-babel-show-result-all
>>         append local]
>>            5]
>>          org-babel-result-hide-spec org-babel-hide-all-hashes)
>>  org-archive-hook '(org-attach-archive-delete-maybe)
>>  org-confirm-elisp-link-function 'yes-or-no-p
>>  org-agenda-before-write-hook '(org-agenda-add-entry-text)
>>  org-metaup-hook '(org-babel-load-in-session-maybe)
>>  org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3
>> "\n\n(fn ENTRY)"]
>>  org-babel-pre-tangle-hook '(save-buffer)
>>  org-tab-first-hook '(org-babel-hide-result-toggle-maybe
>>           org-babel-header-arg-expand)
>>  org-occur-hook '(org-first-headline-recenter)
>>  org-cycle-hook '(org-cycle-hide-archived-subtrees
>> org-cycle-show-empty-lines
>>           org-optimize-window-after-visibility-change)
>>  org-speed-command-hook '(org-speed-command-activate
>>               org-babel-speed-command-activate)
>>  org-dynamic-block-alist '(("columnview" . org-columns-insert-dblock)
>> 

Re: [O] Order of items after a headline in an Org outline?

2019-02-10 Thread Bernt Hansen
David Masterson  writes:

> Is there a documented requirement of the order of things in a Org
> outline?  For instance, do these things have to come directly after the
> headline and, if so, in what order?  Will Org get confused otherwise?
> * PROPERTY drawer
> * Timestamp
> * SCHEDULED and DEADLINE
> * Notes
>
> --
> David

I use M-x org-lint to report problems so I can manually fix them in my
org-files.  Otherwise I don't worry about the ordering.

Regards,
Bernt



[O] Refiling Completion Systems

2019-02-08 Thread Bernt Hansen
Hi,

I've been using org-mode for over ten years and at some point the ido
completion for refiling went away -- probably when refiling functionalty
was rewritten.  Is there a similar completion system available that I
can use to locate my refile targets?  I really liked the ido search with
incremental search refinement (C-SPC) of IDO to limit my targets until I
find the one I want.

I'm currently using

(setq org-refile-use-outline-path t)

but that isn't really working well when I don't remember the parent task
heading :)

I am currently using Org on Windows.

GNU Emacs 25.1.1 (x86_64-w64-mingw32) of 2016-09-17
Org mode version 9.2.1 (release_9.2.1-195-gef1edf @ 
c:/D-Drive/bin/org-mode/lisp/)

Thanks for Org!

Best regards,
Bernt



Re: [O] M-S-RET doesn't work anymore?

2019-01-24 Thread Bernt Hansen
Nicolas Goaziou  writes:

>> May be those keys should be bound to both RET and  variants?
>
> This is what I just did in master. Thank you.

Thanks!!  It works great again :)

I really like the pairing of C-RET, C-S-RET which creates a TODO and
M-RET and M-S-RET which creates a checkbox.  Converting lists to
headings with C-c * and back again with C-c - just feels natural when
the key bindings work this way.

Having to use C-M-S-m just felt awkward and wrong to me :)

Thanks for all your excellent work on Org!

Regards,
Bernt



[O] M-S-RET doesn't work anymore?

2019-01-23 Thread Bernt Hansen
Hi,

I regularly create checkbox lists on the fly with

1. [ ] blah and M-S-RET to create  the second entry

2. [ ] 

But the checkbox is missing today.  Has this functionality changed?

I am running the latest master from git on windows emacs 25.1

Thanks,
Bernt



Re: [O] recent org-mode changes: completion of repeated tasks reports "10 repeater intervals were not enough to shift date past today"

2019-01-15 Thread Bernt Hansen
Daniel Ortmann  writes:

> No other tasks.  Here is the complete text with only one url removed:
>
> * TODO [#C] p6 time entry
>   DEADLINE: <2019-01-18 Fri ++1w -0d>
>   :PROPERTIES:
>   :LAST_REPEAT: [2019-01-11 Fri 17:03]
>   :END:
>   :LOGBOOK:
>


> On 1/13/19 10:12 AM, Bernt Hansen wrote:
>
> Daniel Ortmann  writes:
>
> I have a weekly scheduled task with ...
>   DEADLINE: <2019-01-18 Fri ++1w -0d>
> 
> Recently, when I complete the task it reports the following:
> 
> Clock stopped at [2019-01-11 Fri 17:03] after 0:05
> 10 repeater intervals were not enough to shift date past today. 
> Continue? (y or n) n
> 
> Thoughts?
> 
> Hi Daniel,
> 
> Do you have some other repeating timestamp buried somewhere in that
> task?  It is probably moving that one forward and it is the one that
> needs more than 10 repeats to become current.
> 
> There was a recent change that updates all repeating timestamps in the
> task.
> 
> Regards,
> Bernt

Sorry I can't reproduce what you are seeing.

Regards,
Bernt



Re: [O] please read: bug when marking tasks done

2019-01-15 Thread Bernt Hansen
Samuel Wales  writes:

> dunno best solution.
>
> another option is to comment out repeater intervals like ;.+2d instead
> of .+0d or =[... .+2d]=.
>
> this would also allow you to know what the interval was [currently
> that information is lost].  it would avoid overloading face.  it would
> be under user control for every ts.  it would, however, require
> updating ts regexp.
>
>
> On 1/13/19, Nicolas Goaziou  wrote:
>> Hello,
>>
>> cesar mena  writes:
>>
>>> i'm ok going with the verbatim syntax - rescheduled lines will now look
>>> like (w/o the double quotes?):
>>>
>>>   - Rescheduled from =[2019-02-05 Tue .1m]= on [2018-09-29 Sat 18:50]
>>
>> Thinking about it, another possibility is to add a variable, e.g.,
>> `org-repeat-inactive-timestamps', letting the user choose what to do
>> with inactive time stamps. I think it would default to nil.
>>
>> This would be a more conservative solution; however, this would
>> contradict releases notes for Org 9.2.
>>
>> WDYT?
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>>

I don't have a need for updating any timestamps but the ones in the
SCHEDULED/DEADLINE: entry.  A variable to control behaviour would work
great for me.

Regards,
Bernt



Re: [O] recent org-mode changes: completion of repeated tasks reports "10 repeater intervals were not enough to shift date past today"

2019-01-13 Thread Bernt Hansen
Daniel Ortmann  writes:

> I have a weekly scheduled task with ...
>   DEADLINE: <2019-01-18 Fri ++1w -0d>
>
> Recently, when I complete the task it reports the following:
>
> Clock stopped at [2019-01-11 Fri 17:03] after 0:05
> 10 repeater intervals were not enough to shift date past today. 
> Continue? (y or n) n
>
> Thoughts?

Hi Daniel,

Do you have some other repeating timestamp buried somewhere in that
task?  It is probably moving that one forward and it is the one that
needs more than 10 repeats to become current.

There was a recent change that updates all repeating timestamps in the
task.

Regards,
Bernt



Re: [O] please read: bug when marking tasks done

2019-01-08 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Anyway, I don't really have any other idea besides dropping the repeater
> part from automatically inserted inactive time stamps. 

When I unschedule (and log) a habit I don't want to lose the detail
about the repeat interval.  My workaround for this is to break the
timestamp by adding a ',' after the '[' in the timestamp so marking it
DONE actually works.

** DONE Weekly Review 2018 [0/16]
 CLOSED: [2019-01-08 Tue 09:19]
:PROPERTIES:...
:LOGBOOK:
- State "DONE"   from "TODO"   [2019-01-08 Tue 09:19]
- Not scheduled, was "[,2019-01-07 Mon ++7d/14d]" on [2019-01-08 Tue
09:18]

Marking this task done is also pretty slow - taking 25 seconds.
The task has 233 lines, 2549 words, and 12993 characters.

partial elp-results for this task below

org-todo   1   25.33 25.33
org-self-insert-command1   25.33 25.33
org-checklist  1   25.12425.124
org-reset-checkbox-state-subtree   1   25.12425.124
org-reset-checkbox-state-maybe 1   25.12425.124
org-update-checkbox-count  1   24.94524.945
org-update-checkbox-count-maybe1   24.94524.945
org-element-at-point   154824.87099  0.0160665374
org-element-context154124.86899  0.0161382219
org-element--parse-to  154424.71899  0.0160097150
org-element--current-element   310922.07099  0.0070990672
org-element-example-block-parser   153719.66499  0.0127944046
org-unescape-code-in-string153713.60400  0.0088510084
org-element-paragraph-parser   15441.77  0.0011528497
org-fast-todo-selection1   0.201 0.201
...

Regards,
Bernt



Re: [O] please read: bug when marking tasks done

2019-01-07 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> cesar mena  writes:
>
>> hello everyone,
>>
>> in the maint branch, marking a repeatable task as DONE causes the
>> "Rescheduled from" dates to be lost in the :LOGBOOK:.
>>
>> in the below diff all of the from dates are rewritten with the new
>> scheduled date:
>>
>>   -  SCHEDULED: <2018-12-04 Tue .+1m>
>>   +  SCHEDULED: <2019-02-05 Tue .+1m>
>>  :PROPERTIES:
>>   -  :LAST_REPEAT: [2018-08-08 Wed 07:40]
>>   +  :LAST_REPEAT: [2019-01-05 Sat 18:47]
>>  :END:
>>  :LOGBOOK:
>>   -  - Rescheduled from "[2018-11-28 Wed .+1m]" on [2018-11-28 Wed 08:35]
>>   -  - Rescheduled from "[2018-11-25 Sun .+1m]" on [2018-11-25 Sun 09:17]
>>   -  - Rescheduled from "[2018-11-20 Tue .+1m]" on [2018-11-22 Thu 10:03]
>>   -  - Rescheduled from "[2018-11-13 Tue .+1m]" on [2018-11-17 Sat 09:48]
>>   -  - Rescheduled from "[2018-11-06 Tue .+1m]" on [2018-11-08 Thu 07:02]
>>   -  - Rescheduled from "[2018-10-28 Sun .+1m]" on [2018-10-30 Tue 16:22]
>>   -  - Rescheduled from "[2018-10-25 Thu .+1m]" on [2018-10-25 Thu 07:34]
>>   -  - Rescheduled from "[2018-10-19 Fri .+1m]" on [2018-10-19 Fri 07:48]
>>   -  - Rescheduled from "[2018-10-16 Tue .+1m]" on [2018-10-16 Tue 16:21]
>>   -  - Rescheduled from "[2018-10-11 Thu .+1m]" on [2018-10-14 Sun 10:31]
>>   -  - Rescheduled from "[2018-10-07 Sun .+1m]" on [2018-10-08 Mon 08:48]
>>   -  - Rescheduled from "[2018-09-27 Thu .+1m]" on [2018-09-29 Sat 18:50]
>>   -  - Rescheduled from "[2018-09-20 Thu .+1m]" on [2018-09-20 Thu 09:50]
>>   -  - Rescheduled from "[2018-09-08 Sat .+1m]" on [2018-09-14 Fri 07:10]
>>   +  - State "DONE"   from "TODO"   [2019-01-05 Sat 18:47]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-28 Wed 08:35]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-25 Sun 09:17]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-22 Thu 10:03]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-17 Sat 09:48]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-08 Thu 07:02]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-30 Tue 16:22]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-25 Thu 07:34]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-19 Fri 07:48]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-16 Tue 16:21]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-14 Sun 10:31]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-08 Mon 08:48]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-29 Sat 18:50]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-20 Thu 09:50]
>>   +  - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-14 Fri 07:10]
>>   
>> bisect says it was introduced in
>> af81211fdc01b64449179bcdb77fb1c8ecb3fb94.
>
> Which is a bugfix…
>
> I think a solution would be to remove the repeater from timestamps
> inserted upon logging a state change or a re-scheduling.
>
> However, you would have to fix your old documents manually.
>
> Regards,

Hi Nicholas,

I think this commit is a problem:

  af81211fd (Also obey to repeaters in inactive time stamps, 2018-11-10)

At the beginning of the year I close my repeating tasks with lots of
logging and clocking entries and create a new one as follows:

1) Clone repeating task to new task for next year
2) Unscheduled old task which writes the scheduled repeater to the log
as above
3) Mark old task DONE 

Step 3 fails.  It moves the repeater in the log message from the old
scheduled task makes the task TODO again.

Example:


* TODO Sample repeating task 2018
  SCHEDULED: <2019-01-07 Mon ++1w>
  :LOGBOOK:
  - Note taken on [2019-01-07 Mon 09:44] \\
Log note 2
  - Note taken on [2019-01-07 Mon 09:44] \\
Log note 1
  :END:
  [2019-01-07 Mon 09:44]



Now clone the task with C-c C-x c 1 RET RET


* TODO Sample repeating task 2018
  SCHEDULED: <2019-01-07 Mon ++1w>
  :LOGBOOK:
  - Note taken on [2019-01-07 Mon 09:44] \\
Log note 2
  - Note taken on [2019-01-07 Mon 09:44] \\
Log note 1
  :END:
  [2019-01-07 Mon 09:44]

* TODO Sample repeating task 2018
  SCHEDULED: <2019-01-07 Mon ++1w>
  :LOGBOOK:
  - Note taken on [2019-01-07 Mon 09:44] \\
Log note 2
  - Note taken on [2019-01-07 Mon 09:44] \\
Log note 1
  :END:
  [2019-01-07 Mon 09:44]


Rename the second task to 2019 and unschedule the first task:


* TODO Sample repeating task 2018
  

Re: [O] Org Mode - Organize Your Life In Plain Text!

2018-12-17 Thread Bernt Hansen
David Masterson  writes:

> Bernt Hansen  writes:
>
>> Hi David,
>>
>> Sorry my website on org-mode is stale and I don't currently have time to
>> update it.  I stopped updating it in 2015 after changing jobs and moving
>> to the windows platform (at work).  My main issue is lack of free time
>> to spend on this project.
>>
>> The downloadable org file is actually the result of publishing the org
>> source from my very out-of-date Linux workstation.  The original org
>> file (all versions) is available in the git repository.
>>
>> I'd be happy to answer any questions you have related to the site or my
>> current use of org-mode.  I still work in a similar way described on
>> http://doc.norang.ca/org-mode.html but my agenda and some workflows have
>> evolved a bit from what is described in the document.
>>
>> Regards,
>> Bernt
>
> Thank you for replying.  I'll just ask a few questions and maybe expand
> upon them later.
>
> 1. Are you still working with Emacs/Org from 2015 or have you updated
> (but not updated your paper)?

I am working with the latest git version (master branch) on Windows
running Emacs 25.1.1

$ git describe
release_9.1.14-1065-gdc7477070

(currently 2 commits behind master since I haven't updated today)

>
> 2. If you've updated to Org v9+, did you find significant changes from
> what you documented in your paper?  In other words, will running your
> paper through tangle and trying to use the results with latest Emacs and
> Org be likely to work?  Particularly agendas...

There were some changes:

  - dropping org-structure_template_alist and temporarily using
org-tempo. Sinc then I've switched to C-c , which is much better.

  - org-time-clocksum-format -> org-duration-format

  - refile changes (use caching)
  - change time grid definition in agenda
  - org-finalize-agenda-hook -> org-agenda-finalize-hook

>
> 3. Can you suggest a more detailed manual on the setup and use of
> Agendas?  The agenda manual with Org is not really clear to me.

I am not aware of any other manuals.  When I started I used the
out-of-the-box org-mode agendas (daily, weekly, separate task lists) and
then when I was comfortable with how that worked I started making small
customizations so they worked better for me and this eventually turned
into the setup described on my website.

Regards,
Bernt



Re: [O] Org Mode - Organize Your Life In Plain Text!

2018-12-16 Thread Bernt Hansen
David Masterson  writes:

> I've been reading Bernt Hansen's excellent paper on setting up Org-Mode,
> but I noticed that it is rather dated and was wondering if Bernt is
> watching and plans to update the paper.  In particular, the last version
> of the paper on his website has a couple of things that I think should
> be fixed even if he doesn't do anything further with the paper.
>
> 1. Update the stale screen shots to match the rest of the paper so that
> people can see what you're talking about directly -- they would be very
> helpful.
>
> 2. Embed the version numbers in the paper so that when people download
> the paper, they don't lose the version/date of the paper they
> downloaded.  If I read it right, the paper calls a function which gets
> the version from git.  That won't work if I just download the org file.
>
> Is Bernt watching?

Hi David,

Sorry my website on org-mode is stale and I don't currently have time to
update it.  I stopped updating it in 2015 after changing jobs and moving
to the windows platform (at work).  My main issue is lack of free time
to spend on this project.

The downloadable org file is actually the result of publishing the org
source from my very out-of-date Linux workstation.  The original org
file (all versions) is available in the git repository.

I'd be happy to answer any questions you have related to the site or my
current use of org-mode.  I still work in a similar way described on
http://doc.norang.ca/org-mode.html but my agenda and some workflows have
evolved a bit from what is described in the document.

Regards,
Bernt





Re: [O] Bug: Special property ITEM without stars [9.1.14]

2018-12-14 Thread Bernt Hansen
Allen Li  writes:

> On Thu, Dec 13, 2018 at 6:28 AM Bernt Hansen  wrote:
>>
>> Allen Li  writes:
>>
>> > On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou  
>> > wrote:
>> >>
>> >> This is not satisfying, actually. If every item has a single asterisk,
>> >> you miss hierarchy between headlines in the same tree.
>> >
>> > I don't know what you mean.  Hierarchy is not displayed normally in
>> > agenda view anyway, I don't know why displaying it in agenda column
>> > view via the ITEM property is desirable?
>> >
>>
>> I use hierarchy in my custom agenda view everyday.  Please do not remove
>> this feature.
>
> Apparently I'm missing something.  How are you using hierarchy in an
> agenda view?  Agenda views are flat, e.g.:
>
>   tasks:  TODO [#A] Some task
>   tasks:  TODO [#A] Some task
>   tasks:  TODO [#A] Some task
>   tasks:  TODO Some task
>   tasks:  TODO Some task
>   tasks:  TODO Some task
>
> If I remember correctly, the reason they're flat is that it generally
> doesn't make sense to show the hierarchy because it won't make any
> sense.  For example, the following:
>
> * TODO Project A
> ** Some project A notes
> * Project B
> ** TODO Some task for B
>
> would have this hierarchy in an agenda view if we hypothetically displayed it:
>
>   tasks:  * TODO Project A
>   tasks:  ** TODO Some task for B
>
> which I think is confusing at best (but I can believe is useful for
> some work flows if you're careful).
>


In my custom agenda view for Projects I set 
(org-tags-match-list-sublevels 'indented)

(Tags have been removed for clarity)

Projects
  R:  TODO R Some Release
  R:  .TODO Some Project
  R:  ..TODO Some SubProject
  R:  ...NEXT Some Task
  R:  .TODO Another Project
  R:  ..TODO Another Subproject
  R:  ...TODO Another Subproject
  R:  NEXT Another Task
  R:  ..TODO Another Subproject [2/6]

which matches my actual tasks in Development.org

#+TITLE: Development
* TODO R Some Release
** TODO Some Project
*** TODO Some Subproject
 NEXT Some Task
** TODO Another Project
*** TODO Another Subproject
 TODO Another Subproject
* NEXT Another Task
*** TODO Another Subproject [2/6]
...


Regards,
Bernt





Re: [O] Bug: Special property ITEM without stars [9.1.14]

2018-12-13 Thread Bernt Hansen
Allen Li  writes:

> On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou  
> wrote:
>>
>> This is not satisfying, actually. If every item has a single asterisk,
>> you miss hierarchy between headlines in the same tree.
>
> I don't know what you mean.  Hierarchy is not displayed normally in
> agenda view anyway, I don't know why displaying it in agenda column
> view via the ITEM property is desirable?
>

I use hierarchy in my custom agenda view everyday.  Please do not remove
this feature.

Thanks,
Bernt



Re: [O] Regression - Position of point after capture

2018-12-06 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> Bernt Hansen  writes:
>
>> There is a regression in the master branch.
>>
>> In master if you use
>> M-x org-capture
>> t
>> and save your task with C-c C-c
>> then go to the task with C-u C-u M-x org-capture
>> you end up after the captured task instead of on the headline of the
>> newly captured tasked.
>>
>> On the maint branch C-u C-u M-x org-capture 
>> positions point on the heading of the task.
>
> Fixed. Thank you.
>
> Regards,

Hi!

Verified. :)

Thank you very much for the super-quick fix!

Regards,
Bernt



[O] Regression - Position of point after capture

2018-12-05 Thread Bernt Hansen
Hi,

There is a regression in the master branch.

In master if you use
M-x org-capture
t
and save your task with C-c C-c
then go to the task with C-u C-u M-x org-capture
you end up after the captured task instead of on the headline of the
newly captured tasked.

On the maint branch C-u C-u M-x org-capture 
positions point on the heading of the task.

Thanks for all your great work!

Regards,
Bernt



Re: [O] org--string-from-props

2018-10-29 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> Colin Baxter  writes:
>
>> I think there may be an issue with commit
>> b886ebbc8924916c1e36df00639b3208a1c155a2. Using tables, I now get an error:
>>
>> org--string-from-props: Un-handled `display' value: (space :width 1)
>>
>> which goes away when I revert the commit.
>
> Oops. Fixed. Thank you.
>
> Regards,

Thanks as always for the lightning fast response Nicolas!

I didn't even get a chance to report this issue... was too busy when I
ran into it and just manually inserted my |- separate line in my table
when C-c - didn't work.

Excellent work and much appreciated!!

Best Regards,
Bernt



Re: [O] Bug: org-insert-structure-template leaves point at inconvenient place [9.1.14 (9.1.14-932-gf82a30-elpaplus @ .emacs.d/elpa/org-plus-contrib-20180923/)]

2018-10-02 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> Allen Li  writes:
>
>> org-insert-structure-template (C-c C-,) leaves point at an inconvenient
>> place (X marks the spot):
>>
>> #+begin_example
>> X#+end_example
>>
>> My expectation is that right after inserting the template, I can start
>> typing or yank right into it:
>>
>> #+begin_example
>> X
>> #+end_example
>
> Use `C-o'.
>
> I think the current behaviour is better because you can yank text within
> the newly created block without dealing with a blank line later on.

I also prefer the current behaviour.

I regularly use C-c C-, e C-c ' C-y C-c '

to create and populate my example blocks.  This handles the newline
correctly and does not break the syntax.  This also has the benefit of
properly escaping text that interferes with org's syntax.

When you have text in the kill buffer that looks like org headlines it
pastes outside the example block -- which is proper behaviour when
moving headlines around.

try this:

C-c C-, e C-y
with the following your yank buffer


*** one
some text
*** two
more text


You can't paste that inside

#begin_example
#end_example

or

#begin_example

#end_example

Regards,
Bernt



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

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

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

Me too!

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

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

Regards,
Bernt



Re: [O] How to get <

2018-08-13 Thread Bernt Hansen
Sharon Kimble  writes:

> I'm not sure if this is an org-mode problem or a general emacs one, so if its 
> in the wrong place, sorry, and if you can tell me where it should be placed 
> for a better result, then great. :)
>
> Anyway, I'm writing something that has interspersed things like <>
> or <<10-08-2018>> or <<2018-08-11>>, so there's no set pattern except
> they're all prefaced with <<, but how can I show these in possibly a
> Imenu menu to help in moving about in the document, please.
>
> Or is there some other simpler or easier way of getting these to show in
> a drop-down menu from the menubar please?
>
> Thanks
> Sharon.

Hi Sharon,

How about just
M-x occur <<.*>> RET

Regards,
Bernt



Re: [O] How to move up/down a headline but not the subtree?

2018-07-10 Thread Bernt Hansen
alain.coch...@unistra.fr writes:

> Neil Jerram writes on Thu  5 Jul 2018 11:46:
>
>  > > What I would like to do is to be able to move a headline with
>  > > everything up to (but not including) its first subheading.
>  > >
>  > > Does anyone know how to do that?  
>  > >
>  > > I am also interested in knowing if there are specific (deep?)
>  > > reasons why this seemingly basic operation, which I see as the
>  > > analogous of org-do-promote/demote and perform very often with
>  > > standard (but tedious) emacs editing commands, is not already
>  > > implemented.

This only works if the task you want to deal with is level 2 or greater
(i.e. there is a level 1 task above it)

M-S-left M-right C-c C-w (use refile to move this heading somewhere
else)

This promotes all the subheadings one level and detaches the head from
the following stuff so you can move it alone.

Is that what you are looking for?

I regularly capture single level tasks and refile things into trees
later.  If it's filed wrong changing the structure isn't all that hard
with the above commands.  You just don't want to leave the subtasks
orphaned without a parent task (by skipping a level) so that is why I
promote with sublevels first and then demote just the parent task so it
becomes the same level as the subtasks.

Hope that helps.

Regards,
Bernt



Re: [O] Bug: List of TODOs does not appear in agenda view [9.1.13 (9.1.13-elpaplus @ /Users/mic/.emacs.d/elpa/org-plus-contrib-20180611/)]

2018-06-26 Thread Bernt Hansen
Michaël Chlon  writes:

> Well it is very simple:
>
>   • Open a file ".org" in emacs
>   • press: C-c-a a or C-c-a t and do not see any TODO. I have presed the 
> shortcuts that spacemacs provide but nothing ...
>   • I also try with timestamp and deadline, but nothing appear except the 
> calendar
>
> My test file attached to this mail.
>
> But when I try with emacs alone, i have everything displayed !
>
> Chlon Michaël 
> [] E: mic.a.elle.ch...@gmail.com  
>P: 06 12 90 05 13  
> On juin 26 2018, at 12:17 pm, Nicolas Goaziou  wrote:
>
> Michaël Chlon  writes:
>
> What do you mean with : "ECM demonstrating" ?
>
> A minimal complete example, i.e., a recipe so I can try to reproduce
> your issue.
>
> Open Tracking
Did you add your org file to org-agenda-files with C-c [?
If you have no files in your org-agenda-files variable then your agenda
will be empty.

Regards,
Bernt



Re: [O] Bug: org-toggle-tag always marks buffer modified [9.1.13 (9.1.13-elpaplus @ .emacs.d/elpa/org-plus-contrib-20180618/)]

2018-06-24 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Bernt Hansen  writes:
>
>> This problem still exists when the capture template includes TAGS
>>
>> In the below capture-templates definition the "t" (todo) template works
>> fine but the "m" Meeting template does not allow SPC to enter a space
>> between words when entering the headling for the meeting task.
>>
>> (setq org-capture-templates
>>   (quote (("t" "Todo" entry (file "C:/D-Drive/org/refile.org")
>>  "* TODO %?\n%U\n\n%x\n" :clock-in t :clock-resume t)
>>("m" "Meeting" entry (file
>>   "C:/D-Drive/org/refile.org")
>>  "* TODO %? :MEETING:\n%U\n\n" :clock-in t :clock-resume
>>   t
>
> I re-introduced the problem recently. This is now fixed, with
> a regression test for good measure.

Fix confirmed :)

Thanks,
Bernt



Re: [O] very long table calc expressions ?

2018-06-22 Thread Bernt Hansen
Uwe Brauer  writes:

>> Uwe Brauer  writes:
>
> Hello Bernt,
>> Hi Uwe,
>
>> You can edit or view the table formulas with C-c ' in case that helps.
>> This splits the formulas one per line for editing.
>
> Thanks for pointing this out to me, but I seem unable to do it. 
>
> When I use C-c ' I obtain that very long formula in a special buffer,
> but it is again a long line. Breaking this line and then using C-c C-c
> cuts the second line. So this is not what I was looking for, but maybe I
> misunderstood something fundamental.

When I hit C-c ' in this table

#+TBLNAME: stat-final2
|| Frequency |
|+---|
| SS |   |
| AP | 5 |
| NT | 3 |
| SB |#ERROR |
| MH | 2 |
| NP | 3 |
#+TBLFM: @>$2='(length (org-lookup-all "NP" '(remote(data,@2$2..@>I$2)) 
nil))::@>>$2='(length (org-lookup-all "MH" '(remote(data,@2$2..@>I$2)) 
nil))::@>>>$2='(length (org-lookup-all "SB" '\(remote(data,@2$2..@>I$2)) 
nil))::@$2='(length (org-lookup-all "NT" '(remote(data,@2$2..@>I$2)) 
nil))::@>$2='(length (org-lookup-all "AP" '(remote(data,@2$2..@>I$2)) nil))

I get a new window with this in it:

# Field and Range Formulas
@>$2 = '(length (org-lookup-all "NP" '(remote(data,@2$2..@>I$2)) nil))
@>>$2 = '(length (org-lookup-all "MH" '(remote(data,@2$2..@>I$2)) nil))
@>>>$2 = '(length (org-lookup-all "SB" '\(remote(data,@2$2..@>I$2))
nil))
@$2 = '(length (org-lookup-all "NT" '(remote(data,@2$2..@>I$2))
nil))
@>$2 = '(length (org-lookup-all "AP" '(remote(data,@2$2..@>I$2))
nil))

and I can edit individual lines and then C-c C-c or C-c ' again to exit
and rebuild the formula line on the table.

It seems to reverse the lines every other time I do it which is strange
but it works for me.

Regards,
Bernt



Re: [O] Bug: org-toggle-tag always marks buffer modified [9.1.13 (9.1.13-elpaplus @ .emacs.d/elpa/org-plus-contrib-20180618/)]

2018-06-21 Thread Bernt Hansen
Hi Nicolas,

This problem still exists when the capture template includes TAGS

In the below capture-templates definition the "t" (todo) template works
fine but the "m" Meeting template does not allow SPC to enter a space
between words when entering the headling for the meeting task.

(setq org-capture-templates
  (quote (("t" "Todo" entry (file "C:/D-Drive/org/refile.org")
 "* TODO %?\n%U\n\n%x\n" :clock-in t :clock-resume t)
   ("m" "Meeting" entry (file
  "C:/D-Drive/org/refile.org")
     "* TODO %? :MEETING:\n%U\n\n" :clock-in t :clock-resume
  t

Thanks,
Bernt

Bernt Hansen  writes:

> Hi Nicolas,
>
> Please disregard this bug report.  I can't reproduce it anymore after an
> Emacs restart.
>
> Sorry for the noise.
>
> Regards,
> Bernt
>
> Bernt Hansen  writes:
>
>> Hi Nicholas,
>>
>> This fix breaks my capture templates.
>>
>> commit 593058e4a6270f52fdede2b871a0ee6504944f13
>> Author: Nicolas Goaziou 
>> Date:   Tue Jun 19 09:40:00 2018 +0200



Re: [O] very long table calc expressions ?

2018-06-21 Thread Bernt Hansen
Uwe Brauer  writes:

> #+TBLNAME: stat-final2
> || Frequency |
> |+---|
> | SS | 1 |
> | AP | 5 |
> | NT | 3 |
> | SB | 1 |
> | MH | 2 |
> | NP | 3 |
> #+TBLFM: @>$2='(length (org-lookup-all "NP" '(remote(data,@2$2..@>I$2)) 
> nil))::@>>$2='(length (org-lookup-all "MH" '(remote(data,@2$2..@>I$2)) 
> nil))::@>>>$2='(length (org-lookup-all "SB" '(remote(data,@2$2..@>I$2)) 
> nil))::@$2='(length (org-lookup-all "NT" '(remote(data,@2$2..@>I$2)) 
> nil))::@>$2='(length (org-lookup-all "AP" '(remote(data,@2$2..@>I$2)) 
> nil))::@>>$2='(length (org-lookup-all "SS" '(remote(data,@2$2..@>I$2)) 
> nil))
>
>
> Are there any rules to break this very long expression?

Hi Uwe,

You can edit or view the table formulas with C-c ' in case that helps.
This splits the formulas one per line for editing.

Regards,
Bernt



Re: [O] Bug: Regression - SPC in agenda does not show drawer details [version 9.1.13 (release_9.1.13-819-geb8743 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-06-21 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,

Hi!

> Fixed. Thank you.

Confirmed!  Thanks!!

Org-Mode (and Nicolas) is great! :)

Best regards,
Bernt



Re: [O] Bug: Inherited tags alignment problem in block agendas [9.1.13 (release_9.1.13-751-g9dcc52 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-06-20 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> Bernt Hansen  writes:
>
>
>> There seems to be an issue with inherited tag alignment in block agendas
>> in the master branch.
>>
>> ECM follows.
>
> I cannot reproduce this issue. Was it somehow fixed since your report?
>
> Regards,

Yes this was fixed in a previous commit on master since reporting the
problem.  It is working fine now.

I have another annoying bug I run into once a week which I will report
separately.

Short version:

  In the daily agenda showing a single day
  if you jump back 3 days
  turn on log mode (or set a restriction or start clock check mode)
  and then jump back to today
  you can't turn those modes off again.

  My workaround is to jump back 3 days again to turn it off and then it
  works normally.

Will send an ECM when I have time later this week.

Thanks,
Bernt



Re: [O] Bug: org-toggle-tag always marks buffer modified [9.1.13 (9.1.13-elpaplus @ .emacs.d/elpa/org-plus-contrib-20180618/)]

2018-06-19 Thread Bernt Hansen
Hi Nicolas,

Please disregard this bug report.  I can't reproduce it anymore after an
Emacs restart.

Sorry for the noise.

Regards,
Bernt

Bernt Hansen  writes:

> Hi Nicholas,
>
> This fix breaks my capture templates.
>
> commit 593058e4a6270f52fdede2b871a0ee6504944f13
> Author: Nicolas Goaziou 
> Date:   Tue Jun 19 09:40:00 2018 +0200



Re: [O] Bug: Inconsistent effort handling in clock totals in maint [9.1.13 (release_9.1.13 @ /home/bernt/git/org-mode/lisp/)]

2018-06-19 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Bernt Hansen  writes:
>
>> Nicolas Goaziou  writes:
>
>>> We shot ourselves in the foot when we decided that one part of Org
>>> should consider plain numbers as minutes and the other part as hours.
>>> This is clearly sub-optimal.
>>>
>>> I see no easy way to fix it painlessly. If we change anything, the
>>> easier route to go is having Column View mode consider plain numbers as
>>> minutes, because it only affects ... Column View mode itself.
>>>
>>
>> I'd like to change my vote :)
>> So Cancel the above request about touching the mode line code :)
>
> I applied the change above in "next" branch.

Great!  I will play with it when it gets to master. :)

Regards,
Bernt



[O] Bug: Regression - SPC in agenda does not show drawer details [version 9.1.13 (release_9.1.13-819-geb8743 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-06-19 Thread Bernt Hansen
Hi,

The current master branch has a regression from maint when displaying
task details from the agenda using the SPC key.

I keep my task change details in drawers so when I change a task from
TODO to WAITING I record the details of why it is waiting in the
drawer.  In the maint branch I can hit SPC in the agenda  on a WAITING
task and see the details of what it is waiting for in the maint branch.
This no longer works in master.

ECM follows.

Thanks for org-mode!

Regards,
Bernt

ECM: 

--- test.org ---
#+FILETAGS: TEST
#+STARTUP: content

Regression - SPC in agenda does not show details in drawers

*Keys To Reproduce*

1) Add current file to org-agenda files
   C-c [

2) Show agenda
   C-c a t

3) Move to WAITING task
   C-4 C-n

4) Show task
   SPC

Results in maint branch

#+begin_example
,* WAITING Task two  :WAITING:
  :LOGBOOK:
  - State "WAITING"from "TODO"   [2018-06-19 Tue 10:47] \\
for something
  :END:
,* TODO Task three
#+end_example

Results in master branch

#+begin_example
  ,* WAITING Task two  :WAITING:
:LOGBOOK:...
  ,* TODO Task three

#+end_example

* TODO Task one
* WAITING Task two  :WAITING:
  :LOGBOOK:
  - State "WAITING"from "TODO"   [2018-06-19 Tue 10:47] \\
for something
  :END:
* TODO Task three

--- test.el 
(setq org-log-into-drawer t)

(setq org-todo-keywords
  (quote ((sequence "TODO(t/!)" "NEXT(n/!)" "|" "DONE(d/!)")
  (sequence "WAITING(w@/!)" "HOLD(h@/!)"  "|" "CANCELLED(c@/!)"

(setq org-todo-state-tags-triggers
  (quote (("CANCELLED" ("CANCELLED" . t) ("WAITING") ("HOLD"))
  ("WAITING" ("WAITING" . t))
  ("HOLD" ("WAITING") ("HOLD" . t))
  (done ("WAITING") ("HOLD"))
  ("TODO" ("WAITING") ("CANCELLED") ("HOLD"))
  ("NEXT" ("WAITING") ("CANCELLED") ("HOLD"))
  ("DONE" ("WAITING") ("CANCELLED") ("HOLD")

(setq org-todo-keyword-faces
  (quote (("TODO" :foreground "red" :weight bold)
  ("NEXT" :foreground "blue" :weight bold)
  ("DONE" :foreground "forest green" :weight bold)
  ("WAITING" :foreground "orange" :weight bold)
  ("HOLD" :foreground "magenta" :weight bold)
  ("CANCELLED" :foreground "forest green" :weight bold







Emacs  : GNU Emacs 25.1.1 (x86_64-w64-mingw32) of 2016-09-17
Package: Org mode version 9.1.13 (release_9.1.13-819-geb8743 @ 
c:/D-Drive/bin/org-mode/lisp/)




Re: [O] Bug: org-toggle-tag always marks buffer modified [9.1.13 (9.1.13-elpaplus @ .emacs.d/elpa/org-plus-contrib-20180618/)]

2018-06-19 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Allen Li  writes:
>
>> org-toggle-tag always marks the buffer as modified due to how it is
>> implemented.  It would be better if it did not mark the buffer
>> modified if it does not change anything.  This is annoying for
>> org-depend.el (which is contrib, not officially supported) because the
>> org-blocker-hook set by org-depend.el will mark the buffer modified
>> whenever an agenda view is built/refreshed.
>
> Fixed. Thank you.

Hi Nicholas,

This fix breaks my capture templates.

commit 593058e4a6270f52fdede2b871a0ee6504944f13
Author: Nicolas Goaziou 
Date:   Tue Jun 19 09:40:00 2018 +0200

`org-set-tags' modifies buffer only when necessary

* lisp/org.el (org--align-tags-here):
(org-set-tags): Modify buffer only when necessary.

* testing/lisp/test-org.el (test-org/set-tags): Add tests.

Reported-by: Allen Li 




I have reverted it locally and it works again.

My normal TODO capture template doesn't allow SPC to separate words when
entering the new headline for the task.

The relevant capture template entry is

(setq org-capture-templates
  (quote (("t" "Todo" entry (file "C:/D-Drive/org/refile.org")
 "* TODO %?\n%U\n\n%x\n" :clock-in t :clock-resume t)
...

After opening the capture window and point is moved to the %? position I
type the headline but SPC no longer enters a space.  C-v SPC works but
that is inconvenient.

Thanks,
Bernt



Re: [O] Bug: Archiving creates multiple parent tasks in master [9.1.13 (release_9.1.13-787-g13a09b @ c:/D-Drive/bin/org-mode/lisp/)]

2018-06-19 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> Bernt Hansen  writes:
>
>> Archiving tasks using the master branch with the below configuration
>> creates duplicate "* Archived Tasks" heading each time you archive in
>> the test.org_archive file.
>
> Fixed. Thank you.
>
> Regards,

Confirmed.  Thanks you very much! :)

Regards,
Bernt



Re: [O] Fix org-meta-return for checkbox lists

2018-06-15 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Kaushal Modi  writes:
>
>> Currently if you do M-RET in a checkbox list item, the next item does not
>> become a checkbox automatically. This patch fixes that.
>>
>> I have been using this fix locally for few months. But never got to
>> submitting it as I need to yet write a test for it.
>>
>> Does that patch look good (apart from missing tests). Should I format it
>> w.r.t to next? or master?
>
> IMO, there is nothing to fix. Inserting a checkbox in every item is not
> mandatory.
>
> Furthermore, currently, M-RET inserts a regular item and M-S-RET inserts
> it with a checkbox. With your patch, both M-RET and M-S-RET do the same
> thing, which is sub-optimal.
>
> My vote is to keep the current behaviour.

I agree.  I use lists with mixed checkboxes and no checkboxes and do not
want to enforce checkboxes on every list item.

Thanks,
Bernt



[O] Bug: Archiving creates multiple parent tasks in master [9.1.13 (release_9.1.13-787-g13a09b @ c:/D-Drive/bin/org-mode/lisp/)]

2018-06-06 Thread Bernt Hansen


Hi,

Archiving tasks using the master branch with the below configuration
creates duplicate "* Archived Tasks" heading each time you archive in
the test.org_archive file.

The behaviour in the maint branch is correct and files subsequently
archived tasks under the single main heading.

Thanks for org-mode!

Regards,
Bernt

-- test.el -
(setq org-archive-location "%s_archive::* Archived Tasks")

-- test.org 
#+FILETAGS: TEST
#+STARTUP: content

*Keys To Reproduce*

1) Move to next heading
   C-c C-n

2) Move to next heading
   C-c C-n

3) Archive heading
   C-c C-x C-a

4) Archive heading
   C-c C-x C-a

Results in test.org_archive:

maint branch produces (correct)
#+BEGIN_EXAMPLE
* Archived Tasks
** TODO do something
** TODO foo :BAR:
#+END_EXAMPLE

master branch produces (incorrect)
#+BEGIN_EXAMPLE
* Archived Tasks
** TODO do something
* Archived Tasks
** TODO foo :BAR:
#+END_EXAMPLE

* TODO Test Parent  :PRODUCTION:MISC:
  :PROPERTIES:
  :EFFORT:   15:30
  :END:
** TODO do something
   :PROPERTIES:
   :EFFORT:   15
   :END:
   :LOGBOOK:
   CLOCK: [2018-05-12 Sat 00:26]--[2018-05-12 Sat 00:26] =>  0:00
   CLOCK: [2018-05-12 Sat 00:23]--[2018-05-12 Sat 00:23] =>  0:00
   CLOCK: [2018-05-12 Sat 00:22]--[2018-05-12 Sat 00:22] =>  0:00
   CLOCK: [2018-05-12 Sat 00:22]--[2018-05-12 Sat 00:22] =>  0:00
   CLOCK: [2018-05-12 Sat 00:07]--[2018-05-12 Sat 00:08] =>  0:01
   CLOCK: [2018-05-12 Sat 00:00]--[2018-05-12 Sat 00:04] =>  0:04
   :END:
** TODO foo :BAR:
   :PROPERTIES:
   :EFFORT:   00:30
   :END:




Emacs  : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.1)
 of 2013-01-08 on murphy, modified by Debian
Package: Org-mode version 8.3.1 (release_8.3.1-54-g102def @ 
/home/bernt/git/org-mode/lisp/)



Re: [O] Easy Template does not expand

2018-05-17 Thread Bernt Hansen
"ZHUO QL (KDr2)"  writes:

> I am on the bleeding edge and using the master branch of Org-mode. After 
> updating the source of Org a few days ago, I found the easy template can be 
> expanded by TAB key now, that is:
>
> When I press TAB after typing 
> Version Info:
> GNU Emacs 25.2.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.28) of 2018-02-19, 
> modified by Debian
> Org mode version 9.0.5 (release_9.0.5-86-ga91eae @ 
> /home/kdr2/Work/opensrc/org-mode/lisp/)
>
> Does anybody know what's wrong about this? Thanks.

It's not wrong - it's changed.

There is a new keybinding C-c C-, for inserting templates that replaces
the 

Re: [O] Typo on org-tag-alist

2018-05-15 Thread Bernt Hansen
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:

> Bernt Hansen <be...@norang.ca> writes:
>
>> Nope.  I think you found another one (org-tag-persistent-alist) and
>> fixed that instead.  org-tag-alist is the one I reported.
>>
>> $ git grep -n engroup
>> lisp/org.el:3424:`:startgrouptag', `:grouptags', `:engroup',
>> `:endgrouptag' or
>>
>> Thanks for finding the other one :)
>
> Ah. Fixed too. Thank you.

Confirmed.  Thanks!

Bernt



Re: [O] Bug: Inconsistent effort handling in clock totals in maint [9.1.13 (release_9.1.13 @ /home/bernt/git/org-mode/lisp/)]

2018-05-14 Thread Bernt Hansen
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:

> Bernt Hansen <be...@norang.ca> writes:
>
>> I am fine with plain numbers being interpretted as hours. I don't
>> think we need a second interpretation for it (as minutes).
>
> The second interpretation already exists. "org-colview.el" is the sole
> place where plain numbers are treated as hours. Everywhere else, plain
> numbers are minutes, including in "org-clock.el".
>

OK

I wasn't aware that column view is the only place in org-mode where
plain effort numbers mean hours.  So then if we change anything making
column view in line with the rest of org-mode would get my vote.

>> I don't think changing a bare 15 effort to mean minutes instead of the
>> hours is a good idea - in case existing users already have effort data
>> with plain numbers -- their estimates will change drastically.
>
> I'm not proposing to change anything. I'm just suggesting a new way to
> let users decide what should mean "15" when summing properties in
> Columns View mode.
>
> The issue here is you don't want to change Columns View mode, but
> everything else. Or, more accurately, you want to add another exception
> in plain numbers handling when displaying the mode line. This means
> changing how `org-duration-to-minutes' interprets plain numbers, hence
> the "everything else" part.
>
>> Ideally I think I just want the mode line total to behave the same as
>> the existing column view behaviour as far as plain numbers are concerned
>> if this is easy and not causing more problems than it fixes.
>
> We shot ourselves in the foot when we decided that one part of Org
> should consider plain numbers as minutes and the other part as hours.
> This is clearly sub-optimal.
>
> I see no easy way to fix it painlessly. If we change anything, the
> easier route to go is having Column View mode consider plain numbers as
> minutes, because it only affects ... Column View mode itself.
>

I'd like to change my vote :)
So Cancel the above request about touching the mode line code :)

> We can also change nothing. I have the feeling this issue will bubble up
> from time to time, though.
>
> WDYT?

Okay that all sounds very reasonable :)

I think changing column view to be consistent with the rest of org-mode
is the right way to go if we are changing anything.

The issue is how to alert any users in the wild that are already using
efforts and expecting it to behave as hours in column mode so they can
fix their data if we change the interpretation from hours to minutes to
match the rest of org-mode.

I expect this is really old behaviour and a fix isn't really required.

Personally I will try to move away from using plain numbers as efforts.
I usually mean minutes but will need to fix any values that are
displayed in column mode.

For now I will just find and fix my effort values in my org-files and
try not to create plain numbers as efforts in the future when they are
used in column mode.

My org files are under a git repository so finding the bad entries is
fairly easy for me:

git grep -nHi ':effort:' | grep -v '[0-9]:[0-9]'

Would it be useful to flag plain effort numbers in org-lint so they are
easier to find and fix?  This way if I make more in the future I will
hopefully notice sooner.  I have some zero (0) entries and some empty
entries in my org files -- but maybe that's okay.

>> Otherwise I can live with it -- it's been this way for years I think --
>> and I will just change my effort values to always include both HH:MM and
>> avoid plain numbers.
>
> That's the most reasonable solution, IMO. Note that you can also use
> "3h" instead of the ambiguous "3".

Thanks - I wasn't aware of that option.

So unless someone else feels strongly about this issue we should just
close this bug report and 'do nothing'.

Thanks for listening :)

Regards,
Bernt



Re: [O] Typo on org-tag-alist

2018-05-14 Thread Bernt Hansen
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:

> Hello,
>
> Bernt Hansen <be...@norang.ca> writes:
>
>> I think there is a typo in the output of
>>
>> C-h v org-tag-alist RET
>>
>> ':engroup' instead of ':endgroup'
>
> Fixed. Thank you.

Nope.  I think you found another one (org-tag-persistent-alist) and
fixed that instead.  org-tag-alist is the one I reported.

$ git grep -n engroup
lisp/org.el:3424:`:startgrouptag', `:grouptags', `:engroup',
`:endgrouptag' or

Thanks for finding the other one :)

Regards,
Bernt





Re: [O] Bug: Inconsistent effort handling in clock totals in maint [9.1.13 (release_9.1.13 @ /home/bernt/git/org-mode/lisp/)]

2018-05-14 Thread Bernt Hansen
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:

> Hello,
>
> Bernt Hansen <be...@norang.ca> writes:
>
>>Notice modeline total has [0:05/0:15]
>>So 'do something' has an effort of 15 minutes.  It may be entered wrong 
>> but it is a bare 15 value
>>instead of 15:00 or 00:15
>>
>>:EFFORT:   15
>>
>> 6) Go back to Test Parent
>>C-c C-p
>>
>> 7) Enter column mode
>>C-C C-x C-c
>>
>>Notice the total Effort is 15 hours and 30 minutes
>>Column mode is using the 15 effort as hours not minutes while clocking 
>> uses it as minutes.
>>When I run into this I change the effort value to either 15:00 or 00:15 
>> but it would be better if it was handled consistently.
>
> Unfortunately, this discrepancy has deep roots. For example, the manual
> has this:
>
>   {:}   Sum times, HH:MM, plain numbers are hours.
>
> Changing {:} or effort behaviour could be annoying. We may add another
> summary-type, e.g. {::}, with the following description:
>
>   {::}   Sum times, HH:MM, plain numbers are minutes.
>
> WDYT?

I am fine with plain numbers being interpretted as hours.  I don't think
we need a second interpretation for it (as minutes).

Would it be possible to make the mode line total match whatever the
current column view totalling is?  Since the mode line total is using
plain numbers as minutes not hours.

I am just looking for consistency and existing setups with column view
shouldn't be broken by a change here -- but I doubt anyone depends on
the display on the mode line -- so if that changed from minutes to hours
I would be fine with that.

I don't think changing a bare 15 effort to mean minutes instead of the
hours is a good idea - in case existing users already have effort data
with plain numbers -- their estimates will change drastically.  But
making the effort total on the mode line change from 15 minutes to 15
hours will be consistent with the column view interpretation of plain
numbers and it will be more obvious when you clock in that it isn't what
you are expecting.

OTOH people that don't use column view at all (do we have users like
that?) that use clocking and the current behaviour on the mode line
might be surprised when their total value changes from minutes to
hours... but other than an 'alarm' indicator when you hit the limit it
doesn't really do anything else that is useful as far as I know.

My reason for using efforts is in estimating work on tasks and then
following through and clocking the work to see how good my estimate
really was.  Column view as is works great for that.  I find the mode
line timer showing progress towards my effort limit useful but it is
just a visual indication of how far along I am on the task currently
being clocked -- and it jumps out as being wrong when the effort is a
plain number.

Any existing effort estimates I have with plain numbers are already
hours in the existing column view code and I wouldn't want my estimates
to change all of a sudden because we changed the default plain numbers
from hours to minutes.

Ideally I think I just want the mode line total to behave the same as
the existing column view behaviour as far as plain numbers are concerned
if this is easy and not causing more problems than it fixes.

Otherwise I can live with it -- it's been this way for years I think --
and I will just change my effort values to always include both HH:MM and
avoid plain numbers.

Thanks,
Bernt




[O] Bug: Inherited tags alignment problem in block agendas [9.1.13 (release_9.1.13-751-g9dcc52 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-05-11 Thread Bernt Hansen
Hi,

There seems to be an issue with inherited tag alignment in block agendas
in the master branch.

ECM follows.

Thanks,
Bernt

-- test.el 
--
(setq org-agenda-custom-commands
  (quote ((" " "Agenda"
   ((agenda "" nil)
(tags-todo "-CANCELLED+WAITING|HOLD/!"
   ((org-agenda-overriding-header "Waiting and 
Postponed Tasks")
(org-tags-match-list-sublevels nil)))
(tags-todo "-REFILE-CANCELLED-WAITING-HOLD/!"
   ((org-agenda-overriding-header "Project Subtasks")
(org-agenda-sorting-strategy
 '(category-keep
(tags-todo "-CANCELLED/!"
   ((org-agenda-overriding-header "Projects")
(org-tags-match-list-sublevels 'indented)
(org-agenda-sorting-strategy
 '(category-keep
)
   nil
-- test.org 
--
#+FILETAGS: TEST
#+STARTUP: content

*Keys To Reproduce*

1) Lock agenda to this file
   C-c C-x <

2) Show custom agenda
   Note this is a simplified version of my agenda so the sections don't work
   properly but they show the tags problem

   C-c a SPC

   Note the tags appear both left and right aligned in the block agenda
   It seems file tags and inherited tags are on the left and task tags 
   are on the right.  I was expecting all tags to be aligned on the right.

#+begin_example
Week-agenda (W19):
Monday  7 May 2018 W19
Tuesday 8 May 2018
Wednesday   9 May 2018
Thursday   10 May 2018
Friday 11 May 2018
Saturday   12 May 2018
Sunday 13 May 2018


Waiting and Postponed Tasks


Project Subtasks
  test:   TODO Test Parent :TEST:: :PRODUCTION:MISC:
  test:   TODO do something :TEST::PRODUCTION:MISC::
  test:   TODO foo :TEST: :PRODUCTION:MISC::   :BAR:


Projects
  test:   TODO Test Parent :TEST:: :PRODUCTION:MISC:
  test:   .TODO do something :TEST:   :PRODUCTION:MISC::
  test:   .TODO foo :TEST: :PRODUCTION:MISC::  :BAR:
#+end_example

In maint it looks correct (like this)

#+begin_example
Week-agenda (W19):
Monday  7 May 2018 W19
Tuesday 8 May 2018
Wednesday   9 May 2018
Thursday   10 May 2018
Friday 11 May 2018
Saturday   12 May 2018
Sunday 13 May 2018


Waiting and Postponed Tasks


Project Subtasks
  test:   TODO Test Parent   
:TEST::PRODUCTION:MISC:
  test:   TODO do something  
:TEST:PRODUCTION:MISC::
  test:   TODO foo   
:TEST:PRODUCTION:MISC::BAR:


Projects
  test:   TODO Test Parent   
:TEST::PRODUCTION:MISC:
  test:   .TODO do something 
:TEST:PRODUCTION:MISC::
  test:   .TODO foo  
:TEST:PRODUCTION:MISC::BAR:
#+end_example
* TODO Test Parent  :PRODUCTION:MISC:
  :PROPERTIES:
  :EFFORT:   15:30
  :END:
** TODO do something
   :PROPERTIES:
   :EFFORT:   15
   :END:
   :LOGBOOK:
   CLOCK: [2018-05-12 Sat 00:26]--[2018-05-12 Sat 00:26] =>  0:00
   CLOCK: [2018-05-12 Sat 00:23]--[2018-05-12 Sat 00:23] =>  0:00
   CLOCK: [2018-05-12 Sat 00:22]--[2018-05-12 Sat 00:22] =>  0:00
   CLOCK: [2018-05-12 Sat 00:22]--[2018-05-12 Sat 00:22] =>  0:00
   CLOCK: [2018-05-12 Sat 00:07]--[2018-05-12 Sat 00:08] =>  0:01
   CLOCK: [2018-05-12 Sat 00:00]--[2018-05-12 Sat 00:04] =>  0:04
   :END:
** TODO foo :BAR:
   :PROPERTIES:
   :EFFORT:   00:30
   :END:



Emacs  : GNU Emacs 25.1.1 (x86_64-w64-mingw32)
 of 2016-09-17
Package: Org mode version 9.1.13 (release_9.1.13-751-g9dcc52 @ 
c:/D-Drive/bin/org-mode/lisp/)



[O] Bug: Inconsistent effort handling in clock totals in maint [9.1.13 (release_9.1.13 @ /home/bernt/git/org-mode/lisp/)]

2018-05-11 Thread Bernt Hansen

Hi,

I noticed maint (and master) has inconsistent handling for effort amounts

Below is an ECM to reproduce the behaviour.

Thanks for Org-Mode!

Regards,
Bernt

--- test.org 
-
#+FILETAGS: TEST
#+STARTUP: content

*Keys To Reproduce*

1) Expand window to full screen so you can see the clock modeline total in step 
4

2) Go to first headline
   C-c C-n

3) Go to do something
   C-c C-n

4) Clock in
   C-c C-x C-i

   Notice modeline total has [0:05/0:15]
   So 'do something' has an effort of 15 minutes.  It may be entered wrong but 
it is a bare 15 value
   instead of 15:00 or 00:15

   :EFFORT:   15

6) Go back to Test Parent
   C-c C-p

7) Enter column mode
   C-C C-x C-c

   Notice the total Effort is 15 hours and 30 minutes
   Column mode is using the 15 effort as hours not minutes while clocking uses 
it as minutes.
   When I run into this I change the effort value to either 15:00 or 00:15 but 
it would be better if it was handled consistently.
   
* TODO Test Parent  :PRODUCTION:MISC:
  :PROPERTIES:
  :EFFORT:   15:30
  :END:
** TODO do something
   :PROPERTIES:
   :EFFORT:   15
   :END:
   :LOGBOOK:
   CLOCK: [2018-05-12 Sat 00:23]--[2018-05-12 Sat 00:23] =>  0:00
   CLOCK: [2018-05-12 Sat 00:22]--[2018-05-12 Sat 00:22] =>  0:00
   CLOCK: [2018-05-12 Sat 00:22]--[2018-05-12 Sat 00:22] =>  0:00
   CLOCK: [2018-05-12 Sat 00:07]--[2018-05-12 Sat 00:08] =>  0:01
   CLOCK: [2018-05-12 Sat 00:00]--[2018-05-12 Sat 00:04] =>  0:04
   :END:
** TODO foo :BAR:
   :PROPERTIES:
   :EFFORT:   00:30
   :END:


--- test.el 
--
; Set default column view headings: Task Effort Clock_Summary
(setq org-columns-default-format "%80ITEM(Task) %10Effort(Effort){:} 
%10CLOCKSUM")

(setq org-agenda-clockreport-parameter-plist
  (quote (:link t :maxlevel 9 :fileskip0 t :compact t :narrow 80)))


--

Emacs  : GNU Emacs 25.1.1 (x86_64-w64-mingw32)
 of 2016-09-17
Package: Org mode version 9.1.13 (release_9.1.13 @
 c:/D-Drive/bin/org-mode/lisp/)



[O] Typo on org-tag-alist

2018-05-11 Thread Bernt Hansen
Hi,

I think there is a typo in the output of

C-h v org-tag-alist RET

':engroup' instead of ':endgroup'

Regards,
Bernt



org-tag-alist is a variable defined in .org.el..
Its value is shown below.

Documentation:
Default tags available in Org files.

The value of this variable is an alist.  Associations either:

  (TAG)
  (TAG . SELECT)
  (SPECIAL)

where TAG is a tag as a string, SELECT is character, used to
select that tag through the fast tag selection interface, and
SPECIAL is one of the following keywords: .:startgroup.,
.:startgrouptag., .:grouptags., .:engroup., .:endgrouptag. or
 ^
.:newline..  These keywords are used to define a hierarchy of
tags.  See manual for details.



[O] Bug: Group tag filters repeated per org-file [9.1.13 (release_9.1.13-751-g9dcc52 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-05-11 Thread Bernt Hansen
Hi,

This bug is mainly a visual annoyance when filtering by tag in the
agenda.  It is low priority to fix but I thought I should report it
anyway.

Thanks for all your fabulous work on org-mode!

Regards,
Bernt

--- test.org 
-
*Keys To Reproduce*

1) Add test.org to org-agenda-files 
   C-c [ 

2) open agenda
   C-c a a

3) Filter by tag
   /
   shows 'Filter by tag [123whPfdDQMEc? '
   This is correct.

4) quit filter
   C-g
   
5) Switch back to test.org
   C-x o

6) Add a second org file to org-agenda-files
   C-x C-w test2.org RET
   C-c [

7) Add test.org to org-agenda-files 
   C-c [ 

8) open agenda
   C-c a a

9) Filter by tag
   /
   shows 'Filter by tag [123123whPfdDQMEc? '

   There is an extra '123' filter choice. One per org-agenda-files entry.

   On my setup I have 8 files in my org-agenda-files and '123' is
   repeated 8 times before the other filter options.

   shows 'Filter by tag [123123123123123123123123whPfdDQMEc? '

* TODO Test Parent  :PRODUCTION:MISC:
** TODO do something
** TODO foo :BAR:

--- test.el 
-
(setq org-agenda-tags-todo-honor-ignore-options t)
(setq org-fast-tag-selection-single-key (quote expert))
(setq org-tag-alist (quote ((:startgroup)
("S1" . ?1)
("S2" . ?2)
("S3" . ?3)
(:endgroup)
("WAITING" . ?w)
("HOLD" . ?h)
("PERSONAL" . ?P)
("FS" . ?f)
("DEFECT" . ?d)
("DEV" . ?D)
("QA" . ?Q)
("MISC" . ?M)
("crypt" . ?E)
("CANCELLED" . ?c)
("FLAGGED" . ??
(setq org-tags-match-list-sublevels t)
(setq org-todo-keyword-faces
  (quote (("TODO" :foreground "red" :weight bold)
  ("NEXT" :foreground "blue" :weight bold)
  ("MEETING" :foreground "forest green" :weight bold)
  ("DONE" :foreground "forest green" :weight bold)
  ("WAITING" :foreground "orange" :weight bold)
  ("DELEGATED" :foreground "orange" :weight bold)
  ("HOLD" :foreground "magenta" :weight bold)
  ("PASS" :foreground "forest green" :weight bold)
  ("FAIL" :foreground "red" :weight bold)
  ("CANCELLED" :foreground "forest green" :weight bold
(setq org-todo-keywords
  (quote ((sequence "TODO(t/!)" "NEXT(n/!)" "|" "DONE(d/!)")
  (sequence "WAITING(w@/!)" "HOLD(h@/!)" "|" "CANCELLED(c@/!)" 
"MEETING"

(setq org-todo-state-tags-triggers
  (quote (("CANCELLED" ("CANCELLED" . t))
  ("WAITING" ("WAITING" . t))
  ("HOLD" ("WAITING") ("HOLD" . t))
  (done ("WAITING") ("HOLD"))
  ("TODO" ("WAITING") ("CANCELLED") ("HOLD") ("DELEGATED"))
  ("NEXT" ("WAITING") ("CANCELLED") ("HOLD") ("DELEGATED"))
  ("DONE" ("WAITING") ("CANCELLED") ("HOLD") ("DELEGATED"))
  ("DELEGATED" ("DELEGATED" . t) ("WAITING") ("CANCELLED") ("HOLD"))
  ("PASS" ("WAITING") ("CANCELLED") ("HOLD")



Emacs  : GNU Emacs 25.1.1 (x86_64-w64-mingw32)
 of 2016-09-17
Package: Org mode version 9.1.13 (release_9.1.13-751-g9dcc52 @
 c:/D-Drive/bin/org-mode/lisp/)



Re: [O] Bug: Agenda has no tasks in master [9.1.13 (release_9.1.13-738-g673165.dirty @ c:/D-Drive/bin/org-mode/lisp/)]

2018-05-11 Thread Bernt Hansen
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:

> Hello,
>
> Bernt Hansen <be...@norang.ca> writes:
>
>> I updated to the latest master this morning and my agenda no longer has
>> any tasks in it.
>
> Fixed. Thank you.
>
> Regards,

Confirmed the fix works :)  Thanks for the ultra-quick response!

Regards,
Bernt



[O] Bug: Agenda has no tasks in master [9.1.13 (release_9.1.13-738-g673165.dirty @ c:/D-Drive/bin/org-mode/lisp/)]

2018-05-11 Thread Bernt Hansen

Hi Aaron,

I updated to the latest master this morning and my agenda no longer has
any tasks in it.

I think this commit breaks my agenda:

commit c9dd7a6a9de34b8094ad6a419260fcc1214cc791 (HEAD)
Author: Aaron Ecay 
Date:   Thu May 10 01:35:08 2018 +0100

org-agenda: one-armed .if. -> .when.

* lisp/org-agenda.el (org-agenda-mode):
(org-agenda-undo, org-agenda):
(org-agenda-get-restriction-and-command):
(org-batch-agenda-csv, org-fix-agenda-info):
(org-agenda-get-some-entry-text):
(org-agenda-prepare, org-agenda-finalize):
(org-agenda-fontify-priorities, org-agenda-entry-text-hide):
(org-agenda-list, org-agenda-ndays-to-span):
(org-search-view, org-todo-list):
(org-tags-view, org-modify-diary-entry-string):
(org-agenda-get-day-entries, org-agenda-get-progress):
(org-agenda-get-deadlines, org-prefix-category-max-length):
(org-agenda-format-item, org-agenda-fix-displayed-tags):
(org-compile-prefix-format):
(org-agenda-before-sorting-filter-function):
(org-agenda-limit-interactively, org-cmp-time):
(org-agenda-set-restriction-lock-from-agenda):
(org-agenda-get-represented-tags, org-agenda-filter-apply):
(org-agenda-filter-top-headline-apply):
(org-agenda-remove-filter, org-agenda-compute-starting-span):
(org-unhighlight, org-unhighlight-once):
(org-agenda-show-tags, org-agenda-check-no-diary):
(org-agenda-date-later-minutes, org-agenda-diary-entry-in-org-file):
(org-agenda-add-entry-to-org-agenda-diary-file):
(org-agenda-bulk-unmark, org-agenda-to-appt): Convert .if. without
.else. to .when,. or .unless. in the case of .(if (not ...)).
(org-batch-agenda-csv): Also convert while-catch to dolist.
(org-agenda-prepare): Also simplify a quasiquoted structure.
(org-agenda-entry-text-hide): Also convert a bogus .mapcar. to
.mapc..
(org-compile-prefix-format): Also convert sequential .if.s to
.cl-case..

The following hunk is NOT a one-armed if and you lost the else part
(the last - line):

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index c5f0bbd29..2f93d4b0b 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -4750,13 +4750,13 @@ The prefix arg TODO-ONLY limits the search to
TODO entries."
 (when (and (stringp match) (not (string-match "\\S-" match)))
   (setq match nil))
 (catch 'exit
-  (if org-agenda-sticky
- (setq org-agenda-buffer-name
-   (if (stringp match)
-   (format "*Org Agenda(%s:%s)*"
-   (or org-keys (or (and todo-only "M") "m"))
match)
- (format "*Org Agenda(%s)*" (or (and todo-only "M")
"m")
-  (setq matcher (org-make-tags-matcher match))
+  ;; TODO: this code is repeated a lot...
+  (when org-agenda-sticky
+   (setq org-agenda-buffer-name
+ (if (stringp match)
+ (format "*Org Agenda(%s:%s)*"
+ (or org-keys (or (and todo-only "M") "m"))
match)
+   (format "*Org Agenda(%s)*" (or (and todo-only "M")
"m")
   ;; Prepare agendas (and `org-tag-alist-for-agenda') before
   ;; expanding tags within `org-make-tags-matcher'
   (org-agenda-prepare (concat "TAGS " match))

When I revert this change my agenda works again.

Please fix :)

Thanks,
Bernt

Emacs  : GNU Emacs 25.1.1 (x86_64-w64-mingw32) of 2016-09-17
Package: Org mode version 9.1.13 (release_9.1.13-738-g673165.dirty @ 
c:/D-Drive/bin/org-mode/lisp/)



Re: [O] Orgalist notes

2018-05-06 Thread Bernt Hansen
Eric Abrahamsen  writes:

> And, as always, thank you! This is fairly heroic work -- I say that
> after having made an attempt at orgstruct-mode, and run away screaming.
> And look, no funny indentation!
>
> - Yet a list item with a ridiculous amount of text in it does not wrap
>   into a second list item.
> - Neither does the second list item, despite having an equivalent amount
>   of spurious typing in it.
>
> - And before I get tired of the experiment, here's the same thing with
>  a numbered list.
> - Oh damn, I hit M-RET, and the numbered list turned into an unnumbered
>   list.
>
> No good deed goes unpunished :)

I think you need 2 blank lines between the lists to separate them by
default - otherwise they are treated as one list and the first bullet
defines the type of list (and therefore changes your 1. back to -

Regards,
Bernt



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

2018-05-02 Thread Bernt Hansen
Bernt Hansen <be...@norang.ca> writes:

> I am not really for or against enabling org-tempo by default.  If it's
> not enabled by default and a clear path is documented for how to achieve
> the same thing in ORG-NEWS using yasnippet or some other expansion
> system then that is perfectly okay with me.  If I can't use  anymore I'll just have to retrain my fingers which have been using this
> for 10 years now -- it's doable it will just take me some time :))

So I'm changing my vote :)
I've disabled org-tempo and am in the process of learning to use C-c C-,
instead of 

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

2018-05-02 Thread Bernt Hansen
Hi,

I think there is a typo in ORG-NEWS


Bastien  writes:

>
> Tim Cross  writes:
>
>
>> Consequently, I'm not going to enable org-tempo, instead going for
>> re-training of my fingers to use the new C-c ' binding.
>
> You certainly mean C-c C-,  :)
>


*** Change in the structure template expansion

Org 9.2 comes with a new template expansion mechanism, combining
~org-insert-structure-template~ bound to ~C-c C-'~.


Shouldn't this be ~C-c C-,~  ?

Thanks,
Bernt



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

2018-04-29 Thread Bernt Hansen
Bastien  writes:

> Hi Nicolas,
>
> Nicolas Goaziou  writes:
>
>> You disagreed with me in the first place with commit 71ad7b1. It was my
>> original intent to not load Org Tempo by default.
>
> Sorry if I missed the statement where you explicitely said you thought
> org-tempo should not be enabled by default, I thought it was just an
> oversight and I didn't realize I was in a disagreement with you when I
> pushed this commit -- if I thought so, I'd write to you on the list to
> raise the topic instead of forcing a change through a commit.
>
> Again, I may be wrong in thinking disabling this will cause trouble to
> many users.  Let's just take a moment to see what users think.
>
> Thanks,

Hi Bastien, Nicolas, Rasmus, and list!

So here is my take on this.

org-tempo is the reason I am here on master right now and participating
in this conversation.

I am not really for or against enabling org-tempo by default.  If it's
not enabled by default and a clear path is documented for how to achieve
the same thing in ORG-NEWS using yasnippet or some other expansion
system then that is perfectly okay with me.  If I can't use 

Re: [O] Testing master branch

2018-04-29 Thread Bernt Hansen
Marco Wahl <marcowahls...@gmail.com> writes:

> Bernt Hansen <be...@norang.ca> writes:
>
>> Can I do make uncompiled instead and skip the restart?
>>
>> What do you recommend?
>
> I always rebuild (with "make" or "make test") followed by org-reload
> (C-c C-x !).
>
> Possibly the rebuild can be omitted if you configure variable
> `load-prefer-newer' to t.
>
> Further I recommend to always power off to save energy.

Thanks Marco!

I was not aware of load-prefer-newer and will check it out.

Regards,
Bernt





Re: [O] Testing master branch

2018-04-29 Thread Bernt Hansen
Achim Gratz <strom...@nexgo.de> writes:

> Bernt Hansen writes:
>> I intend to update and track the master branch git repo changes daily in
>> order to identify problems as early as possible.
>>
>> Does it matter if I compile or not for this?
>>
>> Normally I do:
>>
>> git pull
>> make
>> and restart emacs every morning
>>
>> Can I do make uncompiled instead and skip the restart?
>
> I fail to see how the two are related, unless you are talking about
> compiling a new Emacs every morning.

Hi Achim,

I use a pre-canned Emacs for windows at work so I am not ever compiling
emacs -- only the org-mode elisp code using the org-mode makefile after
updating with the latest changes.

I haven't been tracking the development branch of org-mode in about 3
years so I completely forgot about the org-reload function!  Using
org-reload is what I meant by 'restart'.  I had been restarting emacs to
use the latest compiled version of org-mode since starting to track the
master branch a week or two ago when I upgraded from version 8.3.

>
>> What do you recommend?
>
> make up2
>
> Then re-load org in your running Emacs session or restart Emacs as you
> wish.  Note that the up2 target does not install anything if any of the
> tests failed.  If you want to live dangerously, skip the tests and
> install whatever you've got, use the update2 target.

Living dangerously with my live org files at work doesn't sound like a
smart thing to do at this point :)

I'll try make-up2 and org-reload.

Thanks!
Bernt



[O] Testing master branch

2018-04-29 Thread Bernt Hansen
Hi,

I intend to update and track the master branch git repo changes daily in
order to identify problems as early as possible.

Does it matter if I compile or not for this?

Normally I do:

git pull
make
and restart emacs every morning

Can I do make uncompiled instead and skip the restart?

What do you recommend?

Thanks,
Bernt



Re: [O] Bug: Usability for tags in master branch [9.1.12 (release_9.1.12-646-gb08245 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-04-29 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Bastien  writes:
>
 4) SPC now does not work to insert a space after the TODO so I can type my 
 headline
I have to use C-f
>>
>> I still have this issue with current master.
>
>
> Fixed. Thank you.

Confirmed.  Thanks!!!

I am always amazed at how fast bugs are addressed on this project.
Great job!

Bernt



Re: [O] Bug: Usability for tags in master branch [9.1.12 (release_9.1.12-646-gb08245 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-04-27 Thread Bernt Hansen
Bastien <b...@gnu.org> writes:

> Hi Bernt,
>
> glad to read you!
>

Hi Bastien!  I have been away from this list for far too long -- hoping
to correct that.

> Bernt Hansen <be...@norang.ca> writes:
>
>> With the below org file tags handling behaves in a surprising way.
>
> Thanks for the report - just a quick check, do you have these
> issues on the maint branch as well or just on master?

master branch only.  maint works fine.
I have been on maint for a week or two and tried master due to the
pending release plans.

Thanks,
Bernt



[O] Bug: Usability for tags in master branch [9.1.12 (release_9.1.12-646-gb08245 @ c:/D-Drive/bin/org-mode/lisp/)]

2018-04-27 Thread Bernt Hansen

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

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

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

Hi!

With the below org file tags handling behaves in a surprising way.


* TODO Test Parent  :PRODUCTION:MISC:
** TODO foo :BAR:
** keys to reproduce


1) At beginning of line 2 on TODO foo
2) M-ret to insert a new heading before foo
3) S-ret to get TODO keyword
   - auto fills :PRODUCTION:MISC: tags ?
4) SPC now does not work to insert a space after the TODO so I can type my 
headline
   I have to use C-f
5) C-c C-q on this line now removes both tags
   I thought this was a bug but it seems to be removing tags that are defined 
   by the parent tasks and maybe that is intentional
6) When I enter a parent tag C-c C-q MISC RET it is displayed and then removed 
if I do another C-c C-q
   This was surprising to me and I thought tag handling was completely broken
   Until I tried a tag not in a parent task
   try C-c C-q TAB MISC RET
   C-c C-q TAB PRODUCTION RET

Thanks for all your amazing work on org-mode!

Best regards,
Bernt

== minimal.emacs 
==
(add-to-list 'load-path "C:/D-Drive/bin/org-mode/lisp/")
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org)

(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cb" 'org-iswitchb)
== test.el-emacs 
==
(setq org-agenda-tags-todo-honor-ignore-options t)
(setq org-fast-tag-selection-single-key (quote expert))
(setq org-tag-alist (quote ((:startgroup)
("S1" . ?1)
("S2" . ?2)
("S3" . ?3)
(:endgroup)
("WAITING" . ?w)
("HOLD" . ?h)
("PERSONAL" . ?P)
("FS" . ?f)
("DEFECT" . ?d)
("DEV" . ?D)
("QA" . ?Q)
("MISC" . ?M)
("crypt" . ?E)
("CANCELLED" . ?c)
("FLAGGED" . ??
(setq org-tags-match-list-sublevels t)
(setq org-todo-keyword-faces
  (quote (("TODO" :foreground "red" :weight bold)
  ("NEXT" :foreground "blue" :weight bold)
  ("MEETING" :foreground "forest green" :weight bold)
  ("DONE" :foreground "forest green" :weight bold)
  ("WAITING" :foreground "orange" :weight bold)
  ("DELEGATED" :foreground "orange" :weight bold)
  ("HOLD" :foreground "magenta" :weight bold)
  ("PASS" :foreground "forest green" :weight bold)
  ("FAIL" :foreground "red" :weight bold)
  ("CANCELLED" :foreground "forest green" :weight bold
(setq org-todo-keywords
  (quote ((sequence "TODO(t/!)" "NEXT(n/!)" "|" "DONE(d/!)")
  (sequence "WAITING(w@/!)" "HOLD(h@/!)" "|" "CANCELLED(c@/!)" 
"MEETING"

(setq org-todo-state-tags-triggers
  (quote (("CANCELLED" ("CANCELLED" . t))
  ("WAITING" ("WAITING" . t))
  ("HOLD" ("WAITING") ("HOLD" . t))
  (done ("WAITING") ("HOLD"))
  ("TODO" ("WAITING") ("CANCELLED") ("HOLD") ("DELEGATED"))
  ("NEXT" ("WAITING") ("CANCELLED") ("HOLD") ("DELEGATED"))
  ("DONE" ("WAITING") ("CANCELLED") ("HOLD") ("DELEGATED"))
  ("DELEGATED" ("DELEGATED" . t) ("WAITING") ("CANCELLED") ("HOLD"))
  ("PASS" ("WAITING") ("CANCELLED") ("HOLD")

Emacs  : GNU Emacs 25.1.1 (x86_64-w64-mingw32)
 of 2016-09-17
Package: Org mode version 9.1.12 (release_9.1.12-646-gb08245 @ 
c:/D-Drive/bin/org-mode/lisp/)

current state:
==
(setq
 org-agenda-tags-todo-honor-ignore-options t
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-activate
  org-babel-speed-command-activate)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-confirm-shell-link-function 'yes-or-no-p
 org-tab-before-tab-emulation-hook '(org-tempo-complete-tag)
 org-todo-keyword-faces '(("TODO" :foreground "red" :weight bold)
  ("NEXT" :foreground "blue" :weight bold)
  ("MEETING" :foreground "forest green" :weight bold)
  ("DONE" :foreground "forest green" :weight 

Re: [O] DONE repeating events become TODO, not OTHER

2015-09-23 Thread Bernt Hansen
Nick Dokos  writes:

> Ken Mankoff  writes:
>
>> I have repeating events of type OTHER, as in:
>>
>> * OTHER Foo
>>   <2015-09-16 +1w>
>>
>> When I have finished the task for today, I mark it done. Because it is
>> a repeating event, it doesn't actually change to DONE, instead it
>> changes to TODO and adds a :LAST_REPEAT: item in the :PROPERTIES:
>> drawer.
>>
>> How do I tell this specific item, or all OTHER items in general, that
>> after completion it should remain OTHER rather than changing to TODO?
>>
>
> Do you *have* to have a TODO state? If not,
>
> #+TODO: OTHER | DONE
>
> should do the trick. Or you could use multiple
> sets:
>
> #+TODO: TODO INPROGRESS | DONE
> #+TODO: OTHER | COMPLETED
>
> In the latter case, the keywords all have to be different.
> See
>
>(info "(org) TODO items")


Or after defining OTHER has a todo keyword add a property specifying
which next state you want

* OTHER Foo
  :PROPERTIES:
  :REPEAT_TO_STATE: OTHER
  :END:
  <2015-09-16 +1w>

Regards,
Bernt



Re: [O] Agenda Tag filtering - has the behaviour changed?

2015-09-17 Thread Bernt Hansen
Nicolas Goaziou  writes:

> Hello,
>
> Robert Klein  writes:
>
>> Looking through the commit messages this may come from commit
>> 6c6ae990c10dbe7f96b24fccf840fe9f6d81a3b8
>
> Indeed. It seems related to this NEWS entry
>
>   *** Minor refactoring of ~org-agenda-filter-by-tag~
>   Now uses the argument arg and optional argument exclude instead of
>   strip and narrow.  ARG because the argument has multiple purposes and
>   makes more sense than strip now.  The term narrowing is changed to
>   exclude.
>
>   The main purpose is for the function to make more logical sense when
>   filtering on tags now when tags can be structured in hierarchies.

Thanks both.

So was this an intended usability change?  I can probably live with it -
I just need to retrain my fingers -- but it does take longer to achieve
the result I want now since I have to clear the agenda tags before
selecting a new filter and wait for the agenda update each time (my
agenda has lots of entries).

The old behaviour was faster to use.

I haven't done anything with hierarchical tags yet.

Regards,
Bernt



[O] Agenda Tag filtering - has the behaviour changed?

2015-09-16 Thread Bernt Hansen
Hi,

I am a long-time user of org-mode and am currently using the maintenance
release 8.3.1

I noticed that in the agenda the '//' key to filter by tag now adds tags
when used multiple times.  This breaks my normal workflow for quickly
filtering by a specific tag.

In the past I would do:

/ P to filter items for PRODUCTION then
/ D to filter items by DEV

But now the behaviour is

/ P to filter items by PRODUCTION
/ D adds DEV to filtering by PRODUCTION+DEV which returns no items.

Now I have to do // to clear the tag list between filters.

Is this intended behaviour and did I miss the NEWS update on this?

Thanks,
Bernt



Re: [O] How to trigger the clockcheck in an agenda view.

2014-12-06 Thread Bernt Hansen
Rainer Stengele rainer.steng...@online.de writes:

 Am 20.11.2014 um 13:51 schrieb Rainer Stengele:
 Am 27.09.2013 um 15:00 schrieb Carsten Dominik:
 Hello Carsten,
 
 thank you for that. clockcheck is working. But as soon as I get the 
 clockcheck view the scheduled items to disappear in my agenda view.
 I only can get scheduled items or all items in clockchecked view, not both 
 features.
 Any idea?
 Thanks!
 - Rainer
 
 
 Hi again!
 Any hint is much appreciated, even a does not work right now would be 
 welcome although disappointing.
 Thank you.
 Regards, Rainer

Hi Ranier,

I think that is working as designed.  In clock check mode you only get
clock details and gap and overlap reporting.  You can show clocks inline
with C-u l but that will not give you clock check mode.

Regards,
Bernt




Re: [O] Bernt Hansen's

2014-11-23 Thread Bernt Hansen
rene jl...@yahoo.com writes:

 I wonder whether Bernt would agree to turn his config file into an actual
 lisp package that could be available via Elpa?

 I find his code pretty close to what GTD should look like.  There are a few
 things though that could be twicked a bit in order to comply with David
 Allen's new book on Getting Things Done.

 I will try to contact Bernt and ask him to deliver such an org-gtd.el
 package.  That would be great for the orgmode community.

Hi Rene,

I don't have time to maintain an Elpa package of this stuff currently.
This past Friday I just did a 'catch up' in gnus on this mailing list
and skipped 8600+ unread articles (including this one) due to lack of
available time.  Thanks for the email in private that brought this
thread to my attention.

It should be possible to extract the lisp from my document
(http://doc.norang.ca/org-mode.org) and generate a lisp file with C-c
C-v C-t. This is described at the end of
http://doc.norang.ca/org-mode#HowToUseThisDocument

From there you can edit whatever you need to for your settings.

I personally don't want to conform strictly to David Allen's idea of how
GTD should work.  I like to roll-my-own way of doing things and if an
Elpa packaging of this code would require learning and modifying the
workflows to match David Allen's latest book I simply don't have time
for that undertaking.  Someone else is welcome to take that on if they
are interested.

I just discovered late last week that one of my settings relies on a
feature of the org-mode master branch (and has for over a year) and this
change has not been included in any maintenance release of org-mode.
Lots of people have contacted me about the breaking signature change in
org-remove-drawer-at which is posted in my config since I use the master
branch of org-mode.  I think most people will be using official released
versions of org-mode so I'm not sure how best to handle this issue until
Org 8.3 is released which is supposed to include this signature change.
I will probably just document the signature change and provide
alternative code to use in the extracted version for maintenance
releases until 8.3 is created.

Best Regards,
Bernt




Re: [O] Missing commit in maint

2014-11-23 Thread Bernt Hansen
Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Bernt Hansen be...@norang.ca writes:

 The following commit

 6202ec7 (Remove need to declare drawers before using them, 2013-10-20)

 has been in the master branch for over a year but I can't find it in any
 maintenance releases since then.  Is this intentional?

 It is. This is a breaking change, so it is installed in master instead
 of maint.

 I am using the function 

 (defun org-remove-empty-drawer-at (pos)

 in my .emacs setup and this changed signature in the above commit in the
 master branch only a year ago.

 Is this commit supposed to be applied to maint?

 Yes, when Org 8.3 is released.

Thanks for the explanation :)

I will update my document to add an explanation for this until Org 8.3
is released.

Best regards,
Bernt





Re: [O] C-c C-c in table takes 12 seconds

2014-11-23 Thread Bernt Hansen
Karl Voit devn...@karl-voit.at writes:

 * Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
 Hello,

 Hi!

 Could you provide an ECM? I'm unable to reproduce it.

 Yeah, I can do that. However, because I never did this before and I
 suppose this is going to take me at least two hours, I will post it
 whenever I got time to do the ECM.

 Is this correct that for an ECM I have to provide a complete
 (minimal) init.el and Org-mode files?

Hi Karl,

In case it is useful here is what I use for ECMs (I haven't done one in
well over a year though)

This is on my Linux system:

Shell script to start emacs with a minimal setup
,[ minimal-emacs ]
| #!/bin/sh
| TESTEL=
| TESTFILE=/tmp/test.el
| if test -e $TESTFILE
| then
|   TESTEL=-l /tmp/test.el
| fi
| emacs -q -l ~/minimal.emacs $TESTEL $1
`

Minimal .emacs file to enable org-mode from git
,[ minimal.emacs ]
| (add-to-list 'load-path ~/git/org-mode/lisp/)
| ;(add-to-list 'load-path (expand-file-name ~/git/org-mode/lisp))
| (add-to-list 'auto-mode-alist '(\\.\\(org\\|org_archive\\|txt\\)$ . 
org-mode))
| (require 'org)
| 
| (global-set-key \C-cl 'org-store-link)
| (global-set-key \C-ca 'org-agenda)
| (global-set-key \C-cb 'org-iswitchb)
`

I put test settings that show the problem in /tmp/test.el which is
automatically included when I run 'minimal-emacs'.

Hope that helps.

Regards,
Bernt



[O] Missing commit in maint

2014-11-21 Thread Bernt Hansen
Hi!

The following commit

6202ec7 (Remove need to declare drawers before using them, 2013-10-20)

has been in the master branch for over a year but I can't find it in any
maintenance releases since then.  Is this intentional?

I am using the function 

(defun org-remove-empty-drawer-at (pos)

in my .emacs setup and this changed signature in the above commit in the
master branch only a year ago.

Is this commit supposed to be applied to maint? And if not should it be
removed from the master branch so we are not carrying around this change
forever?

Thanks,
Bernt



[O] Problems with habit graph in the master branch

2014-11-21 Thread Bernt Hansen
Hi,

I tried out the master branch today and the habit graph seems to be
broken.

Habits display as normal repeating tasks in commit

40f2b88 (Open outer link on nested links, 2014-11-20)

and work normally in commit

7429f35 (Merge branch 'maint', 2014-10-22)

Sorry I don't have time to track down the problem commit at the moment.

Regards,
Bernt



[O] [PATCH 2/2] Keep window position in agenda when changing todo states

2014-06-14 Thread Bernt Hansen
Allow changing task state in agenda without moving point.  I
use this when reviewing projects weekly and I need to change the
state of some of the tasks.  I found jumping to the top of the
agenda after each state change especially annoying when it causes
the agenda to scroll.
---
 lisp/org-agenda.el |7 ---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index 2d1bafe..d7632b4 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -8907,9 +8907,10 @@ If FORCE-TAGS is non nil, the car of it returns the new 
tags.
(org-agenda-highlight-todo 'line)
(beginning-of-line 1))
   (t (error Line update did not work)))
- (save-restriction
-   (narrow-to-region (point-at-bol) (point-at-eol))
-   (org-agenda-finalize)))
+ (save-window-excursion
+   (save-restriction
+ (narrow-to-region (point-at-bol) (point-at-eol))
+ (org-agenda-finalize
(beginning-of-line 0)
 
 (defun org-agenda-align-tags (optional line)
-- 
1.7.9.48.g85da4d




[O] Two patches I have been using for 6-12 months

2014-06-14 Thread Bernt Hansen
Hi Bastien,

Attached are two patches I use on top of master.  I have been using these
for 6-12 months so I consider them to be well tested.

Please consider including these in the code base.

Thanks,
Bernt




[O] [PATCH 1/2] Remove striction when finding task by id

2014-06-14 Thread Bernt Hansen
Allows find task by id to locate a task outside a current
restriction.  I restrict to subtrees regularly and when I want to
jump to another task outside the current restriction but in the
same file this patch is required to locate the appropriate
heading.  Without this patch point ends up at the top of my
restricted area which is on the wrong task.
---
 lisp/org-macs.el |8 +---
 1 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/lisp/org-macs.el b/lisp/org-macs.el
index ddd6e2e..e6af5da 100644
--- a/lisp/org-macs.el
+++ b/lisp/org-macs.el
@@ -154,9 +154,11 @@ We use a macro so that the test can happen at compilation 
time.
 `(let ((,mpom ,pom))
(save-excursion
 (if (markerp ,mpom) (set-buffer (marker-buffer ,mpom)))
-(save-excursion
-  (goto-char (or ,mpom (point)))
-  ,@body)
+(save-restriction
+  (widen)
+  (save-excursion
+(goto-char (or ,mpom (point)))
+,@body))
 (def-edebug-spec org-with-point-at (form body))
 (put 'org-with-point-at 'lisp-indent-function 1)
 
-- 
1.7.9.48.g85da4d




Re: [O] [PATCH 1/2] Remove striction when finding task by id

2014-06-14 Thread Bernt Hansen
Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Thank you. Could you provide a changelog with that?

 + (save-restriction
 +   (widen)
 +   (save-excursion

 `save-restriction' + `widen' + `save-excursion' = `org-with-wide-buffer'

Sure thing!

I will update and resend both later today.

(and fix the typo in 'restriction' in the subject above)

Thanks,
Bernt



Re: [O] [PATCH 2/2] Keep window position in agenda when changing todo states

2014-06-14 Thread Bernt Hansen
Will check. Thanks. 

Bernt

 On Jun 14, 2014, at 11:51 AM, Bastien b...@gnu.org wrote:
 
 Hi Bernt,
 
 Bernt Hansen be...@norang.ca writes:
 
 Allow changing task state in agenda without moving point.  I
 use this when reviewing projects weekly and I need to change the
 state of some of the tasks.  I found jumping to the top of the
 agenda after each state change especially annoying when it causes
 the agenda to scroll.
 
 I think the bug this patches is supposed to fix (i.e. point jumping
 at the top when changing the state of an agenda item) does not exist
 anymore, neither in the maint branch nor in the master one.
 
 Can you double-check?
 
 Also, `save-window-excursion' is sort of a brute-force approach when
 we only need to save the point position in a window.  There is a big
 warning in `save-window-excursion' docstring that I slowly learned to
 appreciate...
 
 Anyway, I just looked at it quickly, maybe that's a correct fix.
 Thanks for further confirmation.
 
 -- 
 Bastien


Re: [O] [PATCH 2/2] Keep window position in agenda when changing todo states

2014-06-14 Thread Bernt Hansen
Yes you are correct. This patch is no longer required.
Please disregard this patch. 

Thanks,
Bernt

 On Jun 14, 2014, at 1:01 PM, Bernt Hansen be...@norang.ca wrote:
 
 Will check. Thanks. 
 
 Bernt
 
 On Jun 14, 2014, at 11:51 AM, Bastien b...@gnu.org wrote:
 
 Hi Bernt,
 
 Bernt Hansen be...@norang.ca writes:
 
 Allow changing task state in agenda without moving point.  I
 use this when reviewing projects weekly and I need to change the
 state of some of the tasks.  I found jumping to the top of the
 agenda after each state change especially annoying when it causes
 the agenda to scroll.
 
 I think the bug this patches is supposed to fix (i.e. point jumping
 at the top when changing the state of an agenda item) does not exist
 anymore, neither in the maint branch nor in the master one.
 
 Can you double-check?
 
 Also, `save-window-excursion' is sort of a brute-force approach when
 we only need to save the point position in a window.  There is a big
 warning in `save-window-excursion' docstring that I slowly learned to
 appreciate...
 
 Anyway, I just looked at it quickly, maybe that's a correct fix.
 Thanks for further confirmation.
 
 -- 
 Bastien


[O] [PATCH] Remove restriction when locating markers

2014-06-14 Thread Bernt Hansen
* org-macs.el: Remove restriction when locating markers

Allows org-with-point-at to locate point outside the current
restriction.
---
 lisp/org-macs.el |6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/lisp/org-macs.el b/lisp/org-macs.el
index ddd6e2e..96265ec 100644
--- a/lisp/org-macs.el
+++ b/lisp/org-macs.el
@@ -154,9 +154,9 @@ We use a macro so that the test can happen at compilation 
time.
 `(let ((,mpom ,pom))
(save-excursion
 (if (markerp ,mpom) (set-buffer (marker-buffer ,mpom)))
-(save-excursion
-  (goto-char (or ,mpom (point)))
-  ,@body)
+(org-with-wide-buffer
+ (goto-char (or ,mpom (point)))
+ ,@body)
 (def-edebug-spec org-with-point-at (form body))
 (put 'org-with-point-at 'lisp-indent-function 1)
 
-- 
1.7.9.48.g85da4d




Re: [O] please. Hekp me to start

2014-01-19 Thread Bernt Hansen
Hi Nick!

This is an awesome response!

Great job!!

Regards,
Bernt


Nick Dokos ndo...@gmail.com writes:

 Renato renato.pontef...@gmail.com writes:

 Hi,
 I know, ther's a lot of doc around there. But: can someone show me
 the best road map to start using (and learning) org-mode?


 Org is a swiss army knife: if you open up all the blades and try to use
 them at once, you are going to hurt yourself.

 Start with one or two things that are interesting to you and ignore
 everything else: e.g. agenda and TODO lists for organizing your life;
 writing up notes for latex or html export. I mention these two because
 they account for about 95% of my personal usage, but you will have to
 adjust to taste.

 Resist the temptation to learn everything at once. Once you've used org
 for a while for the things that matter to *you*, extensions and further
 uses will come naturally.

 For example, learning about tables comes naturally in the note-taking
 process; then you learn about the spreadsheet and doing data analysis in
 org; then you go on to babel and reproducible research. That might
 lead to citations (a field of active research on the list
 currently). Then you might want to publish your notes so others can read
 them; or start a blog...

 Or you decide to organize your life even more and start clocking all
 your activities; track your habits; go on to quantify your life...

 All of these things and more are possible with org, but just because
 they are possible does not mean that you have to do them all (and
 certainly not all at once) in order to use org productively.

 Just remember: one blade at a time.

 I've past the few days, learning emacs, and now, I think I'm able to
 start using org-mode.

 TIA

 Renato





Re: [O] ATTN: Bernt Hansen, regarding org-mode.org

2013-12-15 Thread Bernt Hansen
Hi David,

This file has been removed since it was a really old copy of the
document.  It seems this is no longer supported by the current export
framework.

Thanks,
Bernt


Loyall, David david.loy...@nebraska.gov writes:

 Hello, Bernt.

 According to your famous org-mode.org document (thank you!) this file:

 http://doc.norang.ca/org-mode.org.html

 ...should be a colorized version of the org source.

 Please take a look at it.  The total filesize seems lower than I’d expect. ;)

 Thanks, cheers,

 --Dave



Re: [O] Show TODO item in table of contents

2013-11-22 Thread Bernt Hansen
Nicolas Goaziou n.goaz...@gmail.com writes:

 Bernt Hansen be...@norang.ca writes:

 This patch 
 4c94c4d (ox-html: Add TODO keyword to TOC entries, 2013-11-06)

 changes the behaviour of HTML TOCs.  I noticed that when I export my
 org-mode document (http://doc.norang.ca/org-mode.html) with this patch
 the TOC no longer has numbering on the items - and it is just displayed
 as a plain list.

 Was this intended?  

 Not really. This is a good ole regression.

 Can this be fixed?

 I pushed a fix. Is it better now?

Much better!  Thanks for the quick fix! :)

Regards,
Bernt



Re: [O] Show TODO item in table of contents

2013-11-21 Thread Bernt Hansen
Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 Bastien b...@gnu.org writes:

 Nicolas Goaziou n.goaz...@gmail.com writes:

 In html export include todo state words in table of contents.

 Would the following patch do the job?

 It does for me!  Thanks

 Applied then.


 Regards,

Hi Nicolas,

This patch 
4c94c4d (ox-html: Add TODO keyword to TOC entries, 2013-11-06)

changes the behaviour of HTML TOCs.  I noticed that when I export my
org-mode document (http://doc.norang.ca/org-mode.html) with this patch
the TOC no longer has numbering on the items - and it is just displayed
as a plain list.

Was this intended?  I prefer the old behaviour with numbered TOC entries
matching the numbered headlines (esp since my TOC in this document is
long)

Can this be fixed?

Thanks and regards,
Bernt




Re: [O] [PATCH] Display a count of items next to each list (or block)

2013-10-01 Thread Bernt Hansen


Bernt Hansen be...@norang.ca writes:

 Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
 writes:

 In order to make Org much nicer to use, I felt we missed a count of items 
 next
 to the lists (or blocks, for multi-block agenda views). Here is a patch to 
 add
 this, depending on the new variable `org-agenda-display-count-of-items'
 (enabled by default).

 The count of items must be updated when you apply tag filtering on lists. The
 patch does it as well.

 This patch doesn't report correct counts when a compact agenda is used
 and you filter by some task that doesn't match any entries in your
 block.

This patch also breaks the default N and P key bindings which skips over
uninteresting lines in the agenda.

Regards,
Bernt




Re: [O] [PATCH] Display a count of items next to each list (or block)

2013-09-28 Thread Bernt Hansen


Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:

 In order to make Org much nicer to use, I felt we missed a count of items next
 to the lists (or blocks, for multi-block agenda views). Here is a patch to add
 this, depending on the new variable `org-agenda-display-count-of-items'
 (enabled by default).

 The count of items must be updated when you apply tag filtering on lists. The
 patch does it as well.

This patch doesn't report correct counts when a compact agenda is used
and you filter by some task that doesn't match any entries in your
block.

The block is empty and shows no tasks but the counter is incorrect.

--8---cut here---start-8---
;; Compact the block agenda view
(setq org-agenda-compact-blocks t)
--8---cut here---end---8---

Filter by some tag not in these blocks

/ TAB PERSONAL RET

--8---cut here---start-8---
Tasks to Refile (15/0)
Stuck Projects (15/1)
--8---cut here---end---8---

If the counts are correct I think this makes a good addition to org-mode.

Regards,
Bernt




Re: [O] Viewing notes in agenda log mode

2013-08-22 Thread Bernt Hansen
Manish mailtomanish.sha...@gmail.com writes:

    On 8/7/13, Manish wrote:
     I like to take notes with z in agenda mode logging progress of
     tasks as I move through the day.  Is it possible today to enable
     viewing these notes (first line only) when log mode is turned on
     the agenda mode the way todo state changes or clock lines are
     shown?
    
    On Wed, Aug 7, 2013 at 1:13 PM, Samuel Wales wrote:
    Hi Manish,
    
    Not sure if you mean showing them as if they were the headline?
    

 Probably I should I have attempted to make a visual example with the
 original post.  Following agenda has two extra lines (#4 and #14) that
 kind of shows what I have in mind.  This would allw me to take notes
 as I go in various tasks and when log mode is enabled, I will not see
 just when the task states changes happened and when the specific tasks
 were clocked but also when specific notes were taken.  In case the
 note is long, we could display first line or a certain number of
 characters.  I think this adds to the end of day
 review/recollection/reconstruction after the fact.  Does it make
 sense?

 Wednesday   x December 20xx
   xxx         0:55.. State:     (DONE) TODO GIS sync up meeting with Rob 
 and Jeff      :GIS:@office::
   xxx        21:34.. State:     (WAITING) WAITING Confirm transfers 
 executed - Merlin  :aws:@office:WORK::WAITING:
   xxx        21:34.. State:     (TODO) WAITING Confirm transfers executed 
 - Merlin     :aws:@office:WORK::WAITING:
xxx        21:34.. Note:      (NOTE) THIS IS A NOTE THAT WAS NEVER TAKEN 
:-)         :aws:@office:WORK::WAITING:
   :      21:35.. State:     (TODO) TODO                           
              :certs:WORK::
   :      21:37.. State:     (DONE) TODO sale and share   
 :delhi:PERSONAL::
   :      21:39.. Closed:     CANCELLED Confirm if it actually 
 transferred   :delhi:PERSONAL::CANCELLED:
   :      21:39.. State:     (CANCELLED) CANCELLED Confirm if it 
 happened   :delhi:PERSONAL::CANCELLED:
   :      21:40.. State:     (TODO) TODO Sale and share                
    :delhi:PERSONAL::
   xx:    21:41.. Closed:     DONE London, UK   
 :lucknow:PERSONAL:SOMEDAY::
   xx:    21:41.. State:     (DONE) DONE London, UK   
 :lucknow:PERSONAL:SOMEDAY::
   xx:    21:41.. Closed:     DONE Day out at Vizag   
 :lucknow:PERSONAL:SOMEDAY::
   xx:    21:41.. State:     (DONE) DONE Day out at Vizag   
 :lucknow:PERSONAL:SOMEDAY::
:  21:44.. Note:      (NOTE) WHY IS IT SO HARD TO FIND GOOD 
PEOPLE!          :DG:@office::WAITING:
   :  21:44.. State:     (WAITING) WAITING New Hires for DG at 
 acceptable cost. :DG:@office::WAITING:
   xxx:       21:45.. Closed:     DONE Make list for DEL and LKO           
              :home:
   xxx:       21:45.. State:     (DONE) DONE Make list for DEL and LKO     
              :home:
   xxx:       21:46.. Closed:     CANCELLED Collect the security amount    
              :home::call:CANCELLED:

Hi Manish,

Try [ in the agenda.

Regards,
Bernt



Re: [O] New exporter and dates in tables

2013-08-09 Thread Bernt Hansen
Hi Carsten!

All of my headings are followed by an inactive timestamp.  I've started
leaving a blank line before the content for the heading so the inactive
timestamp is not exported when timestamps are disabled with the :nil
option.  This works fine for me.

Regards,
Bernt

Carsten Dominik carsten.domi...@gmail.com writes:

 Hi guys,

 did you arrive at a conclusion of this thread, or is this still open?

 Thanks

 - Carsten

 On 16.4.2013, at 09:48, Bastien b...@gnu.org wrote:

 Hi Nicolas,
 
 Nicolas Goaziou n.goaz...@gmail.com writes:
 
 Bastien b...@gnu.org writes:
 
 Nicolas Goaziou n.goaz...@gmail.com writes:
 
 We can widen the definition of `standalone': a standalone timestamp is
 a timestamp belonging to a paragraph that contains only timestamps
 objects.
 
 Great.  If that's possible, then I think that's the best solution.
 
 The following patch should do that. It comes with tests, but it should
 be tested extensively, if only to know if this feature is as useful as
 it seems.
 
 I think I nailed down the root of the confusion.
 
 org-export-with-planning does the job that org-export-with-timestamps
 used to do.  So first of all, org-export-with-timestamps should be an
 alias to org-export-with-planning so that users who customized
 org-export-with-timestamps don't have to change their customization:
 
 (define-obsolete-variable-alias 'org-export-with-timestamps
'org-export-with-planning 24.4)
 
 Today, org-export-with-timestamps does a completely different job,
 more fine-grained than the old org-export-with-timestamps.  I suggest
 to rename it to org-export-with-individual-timestamps and to use the
 latest patch you sent, with a default value of t.  I expect the next
 useful value is 'not-standalone.  But if someone wants to get rid of
 time-stamps in tables or in lists, he now can.
 
 Note that another option is to allow all timestamps, put timestamps you
 don't want to export in a specific drawer (e.g. TIME), and ignore this
 drawer during export.
 
 Yes, but that requires educating users, which I don't really like.
 
 Thanks,
 
 -- 
 Bastien



Re: [O] Clocktable time Information without days (8.0) [7.9.2 (7.9.2-dist @ /usr/share/emacs/site-lisp/org/)]

2013-07-27 Thread Bernt Hansen
Hi Arne,

I also don't use the output format that includes days.

Try setting the following variable:

(setq org-time-clocksum-format
  '(:hours %d :require-hours t :minutes :%02d :require-minutes t))

Regards,
Bernt

Arne Babenhauserheide arne_...@web.de writes:

 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-Hackers,

 Since the update to org-mode 8.0¹ my timestamps show a day column, when
 the time is longer than 24 hours. Since I use them to check a 40h
 workweek, that gets in my way quite a bit. I think that I can get used
 to it, but I would prefer to set it back to showing hours as highest unit.

 Is there a way to tell org-mode to avoid showing days? This also
 interferes with plotting via gnuplot (which does not know the day
 format).

 Best wishes,
 Arne

 PS: Sorry for abusing the report-bug function for this. It was the
 fastest way to create this mail…


 ¹: I write this from another computer which still has org 7.

 Emacs  : GNU Emacs 24.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.12)
  of 2013-03-20 on kaverne
 Package: Org-mode version 7.9.2 (7.9.2-dist @ /usr/share/emacs/site-lisp/org/)



Re: [O] [html] non-lists showing up as lists

2013-06-06 Thread Bernt Hansen
Samuel Wales samolog...@gmail.com writes:

 I don't recall whether I said I had a filling problem.

 Filling is a red herring for my use case.

 My point is that regardless of filling, it would be a good idea to be
 stricter about what a list is, for the reasons I listed.  In my use
 case.

 Samuel

Hi Samuel,

I use org indent mode all the time so most of my lists start in column
0.  Requiring an indent will break my existing org data (which goes back
years now) so I don't want indented lists to be a requirement if it is
not absolutely necessary.

Just my two cents.

Regards,
Bernt



Re: [O] New exporter - publishing org files doesn't include :tangle

2013-04-26 Thread Bernt Hansen
Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 Bernt Hansen be...@norang.ca writes:

 So far my attempts using this workaround have failed and I can't get
 :tangle in my exported org file.  I think I also would prefer to have
 the :exports value in the .org source as well so it's a true
 representation of the source.

 There was a bug in org back-end: affiliated keywords were
 removed. I fixed it. Does it solve your problem (using the workaround)?

Thanks!

I'll try again tonight and let you know.

-Bernt



Re: [O] Clocking totals in agenda view

2013-04-26 Thread Bernt Hansen
Rick Moynihan rick.moyni...@gmail.com writes:

 Yes I'd seen that, but I hadn't thought that I could narrow the agenda
 to a day, and then generate the report... which almost gives me what I
 want.

 Ideally I'd like to visualise the clocking times for a whole week at a
 time, by day...  So I could spot days easily where there had been
 clocking errors... rather than having to page through them manually...
 is this possible?

Hi Rick,

I do this on the weekly agenda looking at the entire week with clock
check and Clock check enabled (C-c a a w v c R)

This gives me a quick clock view for the entire week and a total report
for the week.  Then I switch to day view and look at each of the days in
the week one at a time for daily totals (d, f and b to move forward and
back).  It's not all in one place but it works great for my needs and
it's quick to generate.

You can also limit the report to specific tags with C-u R (whatever tags
you are currently filtering with)

Hope that helps.

Regards,
Bernt



Re: [O] New exporter - publishing org files doesn't include :tangle

2013-04-26 Thread Bernt Hansen
Bernt Hansen be...@norang.ca writes:

 Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 Bernt Hansen be...@norang.ca writes:

 So far my attempts using this workaround have failed and I can't get
 :tangle in my exported org file.  I think I also would prefer to have
 the :exports value in the .org source as well so it's a true
 representation of the source.

 There was a bug in org back-end: affiliated keywords were
 removed. I fixed it. Does it solve your problem (using the workaround)?

 Thanks!

 I'll try again tonight and let you know.

 -Bernt

Yes I think this now works.  The :exports details are missing but it's
usable for generating a emacs.el file now from the document.

Thanks!

Bernt



Re: [O] Tracking flexitime

2013-04-26 Thread Bernt Hansen
Thomas Koch tho...@koch.ro writes:

 I'm searching for best practices to track flexi time with orgmode. I've a 
 work 
 contract of 8 hours per day in average. So I'd like to start a clock when I 
 arrive at work, pause it for lunch and stop it when I leave.

 I wouldn't like to rely only on the sum of the time spent on tasks since 
 there 
 is always work time that can hardly be assigned to a specific task.

Hi Thomas,

I clock my 7.5 hour work day every day.  When I arrive at work I punch
in with f9-I which starts the clock on my default * Organization task
then I pick something from the agenda, clock it in and work.

In my setup clocking out moves the clock up one level in the tree or
back to the * Organization task.  This keeps time on projects and works
great for me.

I clock out at lunch (f9-O), clock back in after lunch (f9-I) and clock
out at the end of the day when my daily clock report on the agenda hits
7.5 hours.  I don't get paid for unauthorised overtime and I don't work
for free :)

I clock every minute of every day that I work minus lunch.  If personal
tasks interrupt work I clock those in with a new capture task and remove
these from my daily work report (C-u R in the agenda will show a clock
report using the current tag filter on the agenda).

All the gory details for my setup are here:
http://doc.norang.ca/org-mode.html

Regards,
Bernt



Re: [O] Kill all items with specific tag to kill-ring.

2013-04-25 Thread Bernt Hansen
Oleksandr Gavenko gaven...@gmail.com writes:

  I want this feature in order to simplify precess of moving entries from job
  org-file to home org-file by marking entries with tag :HOME:...

Hi Oleksandr,

If all you want to do is move items why not use the agenda?  Mark your
entries with a tag, do an agenda search for that tag, mark all entries
with m and move them using bulk refile with B r

Regards,
Bernt



Re: [O] Filling bug with alphabetical lists

2013-04-25 Thread Bernt Hansen
Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 Bernt Hansen be...@norang.ca writes:

 Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 Bernt Hansen be...@norang.ca writes:

 I found the following filling bug with alphabetical lists.

 I have 

 (setq org-alphabetical-lists t)

 This is now `org-list-allow-alphabetical'. I think you need to reload
 Org when this variable is changed.

 Thanks, I wasn't aware of this rename but it is already set to t here.
 I'll rename the variable in my .emacs.

 Do you get the same filling behaviour as me?

 Not anymore after I reload Org.

Thanks Nicolas,

My problem was I had org-alphabetical-lists defined _after_ the requires
for the exporter back ends in my .emacs so this didn't work for me.

Putting it before 

--8---cut here---start-8---
;; Explicitly load required exporters
(require 'ox-html)
(require 'ox-latex)
(require 'ox-ascii)
--8---cut here---end---8---

and restarting Emacs fixed it for me.

Regards,
Bernt



Re: [O] New exporter - publishing org files doesn't include :tangle

2013-04-25 Thread Bernt Hansen
Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 Bernt Hansen be...@norang.ca writes:

 James Yuan noticed that the .org file that is published with my document
 (http://doc.norang.ca/org-mode.org does not contain :tangle on any of
 the source blocks.

 One of the uses of this document is to pull up the file and tangle it to
 create an emacs configuration but this seems to be broken in 8.0.

 This is not directly related to the export framework.

 For some reason, Babel removes all properties from the opening string of
 a block when evaluated. IOW

   #+BEGIN_SRC emacs-lisp :exports code :tangle yes
   (+ 1 1)
   #+END_SRC

 becomes

   #+BEGIN_SRC emacs-lisp 
   (+ 1 1)
   #+END_SRC

 One workaround is to add Babel properties on a #+header: affiliated
 keyword instead as

   #+header: :tangle yes
   #+BEGIN_SRC emacs-lisp :exports code
   (+ 1 1)
   #+END_SRC

 becomes

   #+header: :tangle yes
   #+BEGIN_SRC emacs-lisp
   (+ 1 1)
   #+END_SRC


 Regards,

Hi Nick,

So far my attempts using this workaround have failed and I can't get
:tangle in my exported org file.  I think I also would prefer to have
the :exports value in the .org source as well so it's a true
representation of the source.

I'll give this another try again later.

Regards,
Bernt



[O] New exporter - publishing org files doesn't include :tangle

2013-04-24 Thread Bernt Hansen
Hi Nicolas,

James Yuan noticed that the .org file that is published with my document
(http://doc.norang.ca/org-mode.org does not contain :tangle on any of
the source blocks.

One of the uses of this document is to pull up the file and tangle it to
create an emacs configuration but this seems to be broken in 8.0.

I'm using 

--8---cut here---start-8---
   :publishing-function (org-html-publish-to-html 
org-org-publish-to-org)
--8---cut here---end---8---

Regards,
Bernt



Re: [O] Org clock markers are not consistent with org-clock-history

2013-04-24 Thread Bernt Hansen
Bastien b...@gnu.org writes:

 I removed the forward char ugly hack--I cannot reproduce the
 error I was seeing before when the user manually inserts some
 text right on the marker and modifies it in the wrong direction.

 I will try to reproduce the problem later on, but lets use the
 clean way for now.

 Thanks!

Thanks!  Works for me again :)

Regards,
Bernt



  1   2   3   4   5   6   7   8   9   10   >