logrepeat only logging LAST_REPEAT

2021-01-19 Thread Michael Heerdegen
Hello, for some entries I use the logrepeat feature (enabled by setting the LOGGING property of the entry). I get a :LAST_REPEAT: property that I (always) want, and also a complete log I do not (always) want, in the form of a growing list of - State "DONE" from "XYZ" [2021-01-19 Di 12:01]

Re: org-agenda-get-timestamps and properties

2020-11-28 Thread Michael Heerdegen
Kyle Meyer writes: > > but not when formatted like this: > > > > ** APPT 10:40 Xyz > > SCHEDULED: <2020-11-08 So +1d> > > :PROPERTIES: > > :ID: 1d313f9a-3044-4c23-9278-422646ec9063 > > :END: > > > > although the latter form is, AFAICT, recommended, and at least it's what >

org-agenda-get-timestamps and properties

2020-11-10 Thread Michael Heerdegen
Hi, I have a problem with my appt.el replacement I develop. When debugging, I found that `org-agenda-get-timestamps' does, depending on the position of the SCHEDULED spec, do return a timestamp when an entry is formatted like this: ** APPT 10:40 Xyz :PROPERTIES: :ID:

Re: org-marker vs. org-hd-marker

2020-10-29 Thread Michael Heerdegen
Kyle Meyer writes: > Going through each of the collection functions at the end of > org-agenda-get-day-entries, it looks like they all set org-marker. > Plus, I can spot places in org-agenda.el that rely on agenda entries > having org-marker (e.g., org-agenda-goto and org-agenda-todo), so I >

Re: Headline generation as in diary?

2020-10-28 Thread Michael Heerdegen
I wrote: > With diary, I can use arbitrary Lisp expressions to generate dates, and > those expressions can also return a string to use as non-nil return > value to generate non-constant headlines including certain numbers for > example. [...] My solution so far: I've set up my

Re: org-marker vs. org-hd-marker

2020-10-27 Thread Michael Heerdegen
Kyle Meyer writes: > My reading (which could be very wrong) is that org-hd-marker is always > set to the start of the headline. org-marker, on the other hand, is set > to some position in the entry that depends on who is setting it. Thanks for the insights, Kyle. Do you know whether I can

Re: Force creation of org id in template

2020-10-26 Thread Michael Heerdegen
gusbrs.2...@gmail.com writes: > Untested, but how about adding something like the following to your > template? > > :PROPERTIES: > :ID: %(org-id-new) > :END: I'm not sure. I see that creating an id involves slightly more than adding the property - see the `org-id-add-location' call in

Force creation of org id in template

2020-10-26 Thread Michael Heerdegen
Hello, is it possible to tweak `org-capture-templates' entries so that the creation of an org id for an org entry created with `org-capture' is forced? TIA, Michael.

org code and error catching

2020-10-26 Thread Michael Heerdegen
Hello, I had a hard time to debug some problem with the expansion of some capture template because org catched the error even when I had set `debug-on-error'. Would it be possible to make some functions, e.g. `org-eval' in my case (probably some more?), use `condition-case-unless-debug' instead

org-marker vs. org-hd-marker

2020-10-26 Thread Michael Heerdegen
Hello, what's the difference between org-marker and org-hd-marker markers? What does "hd" stand for? TIA, Michael.

Re: Headline generation as in diary?

2020-09-03 Thread Michael Heerdegen
Ihor Radchenko writes: > > I didn't know that eval specs support multi-line sexps, but seems that > > works, so I can indeed use this. Thanks for the suggestion. > > Hmm. According to manual, it should support multi-line string. Not sure > about sexps. AFAIR it didn't work in the past. I

Re: Headline generation as in diary?

2020-09-03 Thread Michael Heerdegen
Ihor Radchenko writes: > I do not think there is support of multi-line planning everywhere. I see. > You can always use file-local definition at the beginning or end of your > org file. Below is an example of local definition at the end of an org > file. > > # Local Variables: > # eval: (defun

Re: Headline generation as in diary?

2020-09-03 Thread Michael Heerdegen
Robert Pluim writes: > It can? Thatʼs not documented, as far as I can tell. As a user, I read "Diary-style expression entries" in the org manual as including my own defined diary sexps - excluding them would be a surprise that should be documented (no, I don't want that to happen!). Michael.

Re: Headline generation as in diary?

2020-09-03 Thread Michael Heerdegen
Ihor Radchenko writes: > > When dealing with complicated date rules it can likely happen that a > > diary sexp doesn't fit into one line. > > Diary sexp can be a user-defined function. If your sexp needs to span > multiple lines, it is probably worth defining a function and simply > using

Re: Headline generation as in diary?

2020-09-03 Thread Michael Heerdegen
Robert Pluim writes: > I can push my change to org, but Iʼm not a regular org contributor, so > Iʼd prefer to hear from one of the maintainers first. Sorry - I meant, I see no reason to touch the existing code. No need to change anything for what I want. > Michael> This doesn't work: > >

Re: Headline generation as in diary?

2020-09-02 Thread Michael Heerdegen
Robert Pluim writes: > OK. Thatʼs as far as my org-hacking knowledge goes, so perhaps someone > else here has an idea of the right way to invoke "tell me what heading > Iʼm in, as a string". The situation is actually like this: the empty string issue doesn't happen with time stamps <%%(...)>,

Re: Headline generation as in diary?

2020-09-02 Thread Michael Heerdegen
Robert Pluim writes: > How about: > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > index 78fe13303..9049b3a42 100644 > --- a/lisp/org-agenda.el > +++ b/lisp/org-agenda.el > @@ -5772,7 +5772,7 @@ displayed in agenda view." > r (replace-match "" nil nil r))) >

Re: Headline generation as in diary?

2020-09-01 Thread Michael Heerdegen
Robert Pluim writes: > Itʼs triggered by the %%(, I believe, but not in headlines. Yes, I see that in the code. But actually I seem to have the opposite problem: I can't make the original headline appear in the agenda. When the sexp doesn't return a string the agenda will contain a line

Re: Headline generation as in diary?

2020-09-01 Thread Michael Heerdegen
Michael Heerdegen writes: > > [1] https://github.com/m-cat/org-recur > > Thanks for the hint, I'll have a look. Nice to have definitely. I want to stick to diary sexp expressions for some complicated dates. I have already extended the diary language to fit my needs to speci

Re: Headline generation as in diary?

2020-09-01 Thread Michael Heerdegen
Eric S Fraga writes: > No, not necessarily. I have entries like this: > > %%(diary-anniversary 1981 03 17) Somebody's birthday (%d years) > > and the agenda view shows "Somebody's birthday (19 years)"; the actual > heading for this entry is ignored. Where in an entry do you specify such

Headline generation as in diary?

2020-09-01 Thread Michael Heerdegen
Hi, I am mainly using the org agenda for day planning. But there is a functionality I seem to miss I know from diary: With diary, I can use arbitrary Lisp expressions to generate dates, and those expressions can also return a string to use as non-nil return value to generate non-constant

Re: Emacs bug 37890; killing capture buffer

2019-12-19 Thread Michael Heerdegen
Ihor Radchenko writes: > You can try M-x org-submit-bug-report ;) > Then it becomes clear that you are in the right place already. Thanks! I didn't know about this command - actually I had searched for it but didn't find it because I had searched for something named "report-org-bug" (analogue

Bug: About org-submit-bug-report [9.3 (release_9.3 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

2019-12-19 Thread Michael Heerdegen
Hello, I want to suggest to make `report-org-bug' and alias for the command `org-submit-bug-report'. That's the name I expected (considering "report-emacs-bug"), also some other Emacs packages name their bug reporting command according to this scheme. The additional name would make this

Re: Emacs bug 37890; killing capture buffer

2019-12-19 Thread Michael Heerdegen
Samuel Wales writes: > the indirect buffer capture mechanism was to be an improvement on > remember.el, and replaced it. you might still be able to find > remember.el if you prefer the separate file idea. I find it acceptable once it's been made more secure (e.g. by using hooks like I

Re: Emacs bug 37890; killing capture buffer

2019-12-19 Thread Michael Heerdegen
Adam Porter writes: > People do care! But everyone here works on Org in their spare time, > and Org is a big project, and things slip through the cracks. I didn't meant to criticize anyone (I have the same problem with my own stuff). Anyway, we got some attention now, thanks for your help!

Re: Emacs bug 37890; killing capture buffer

2019-12-17 Thread Michael Heerdegen
Adam Porter writes: > I guess you're asking me, since I'm the only other person in this > thread--but I'm not an Org maintainer, so my opinion isn't very > important. IMO, the hooks are worth considering, however they should be > done very, very carefully, because bad things can happen when

Re: Emacs bug 37890; killing capture buffer

2019-12-16 Thread Michael Heerdegen
Michael Heerdegen writes: > - kill-buffer-hook in the capture buffer could be used to prevent the > user from killing such a buffer by accident. Or it could be made > configurable what to do (e.g. undo the change with or without user > prompting, ask for what to do, etc.) >

Re: Emacs bug 37890; killing capture buffer

2019-12-15 Thread Michael Heerdegen
Adam Porter writes: > Michael Heerdegen writes: > > > Or (really better IMHO) consider a different implementation where the > > original buffer is not modified until the user explicitly confirms the > > stuff to capture with C-c C-c. > > That would be helpful in so

Emacs bug 37890; killing capture buffer

2019-12-13 Thread Michael Heerdegen
Hi, I want to speak about my Emacs bug report 37890 about org-capture. Seems my main point: | I want to capture an APPT with `org-capture'. I the pop-up buffer to | edit the item I move the date to the second line and add text after the | date (personal preference). That loses the final

Re: [O] Show APPTs every day in Agneda

2019-05-28 Thread Michael Heerdegen
Neil Jerram writes: > #+BEGIN_EXAMPLE > ** Bank holiday weekend > > <2018-05-05 Sat>--<2018-05-07 Mon> > #+END_EXAMPLE > Sorry, that's no solution for you, but maybe there's a clue in the > detail there? Ha! - indeed. It's obviously not allowed to add spaces like I used to do: <2018-05-05

Re: [O] Show APPTs every day in Agneda

2019-05-27 Thread Michael Heerdegen
Neil Jerram writes: > Hi Michael, Hi Neil! > I'm not in front of my computer, to check this, but I think that an > active date range will have this effect, i.e. > > ** Vacation > -- Hmm, no, AFAICT that's what I used to do, and it only shows the appointment at start and end date, not between

[O] Show APPTs every day in Agneda

2019-05-26 Thread Michael Heerdegen
Hi, I've APPTs like "Vacation" that last 14 days or so. Is there an option/way to show such an APPT for every concerned day, and not only for the border days, so that when I for example want to make a doctor's appointment I see for the respective day that I'm on vacation on that day? TIA,

[O] bug#18663: 25.0.50; Org agenda broken due to removed fancy-diary-display alias

2014-10-12 Thread Michael Heerdegen
Hello, I'm not anymore able to view the org agenda. I have been told that this issue has been fixed in the org repo, Commit 4a872ae3... [PATCH] Fix: Emacs 25 fancy diary inclusion in agenda Date: Sat Oct 11 18:16:36 2014 +0200 Dunno when this change will arrive in Emacs and who is

[O] bug#18035: Linum-mode + org-indent-mode results in graphical bug

2014-07-17 Thread Michael Heerdegen
Eli Zaretskii e...@gnu.org writes: [...] I'm not sure this is the same problem as reported by the OP, so it probably should have been reported as a separate bug (merging them later is easy). Ok. I wasn't sure what would be best. - visit a file under version control (I tried a git

[O] bug#18035: Linum-mode + org-indent-mode results in graphical bug

2014-07-16 Thread Michael Heerdegen
Eli Zaretskii e...@gnu.org writes: Activating both linum-mode and org-indent-mode will cause several graphical glitches in the current line. See http://lists.gnu.org/archive/html/emacs-orgmode/2011-01/msg01204.html That discussion provides no reproducible recipe. FWIW, I think we see

[O] bug#18035: Linum-mode + org-indent-mode results in graphical bug

2014-07-16 Thread Michael Heerdegen
Michael Heerdegen michael_heerde...@web.de writes: Activating both linum-mode and org-indent-mode will cause several graphical glitches in the current line. See http://lists.gnu.org/archive/html/emacs-orgmode/2011-01/msg01204.html That discussion provides no reproducible recipe

Re: [O] Bug: Messaging when moving in the agenda [7.9.2 (7.9.2-GNU-Emacs-24-3 @ /usr/share/emacs/24.2.50/lisp/org/)]

2013-09-02 Thread Michael Heerdegen
Hi Carsten, I believe I have done it in the right place now, please confirm. Confirmed, thanks, that's what I wanted. There's just a little typo in the docstring of `org-unlogged-message': Display a message, but avoid loggin it in the *Messages* buffer. ^

Re: [O] Bug: Messaging when moving in the agenda [7.9.2 (7.9.2-GNU-Emacs-24-3 @ /usr/share/emacs/24.2.50/lisp/org/)]

2013-08-06 Thread Michael Heerdegen
Hello, When I move around in the *Org Agenda* with up and down, the current outline path is displayed in the echo area, which is good. However, what is displayed gets also copied in the *Messages* buffer, which is not helpful, but clutters *Messages* with useless noise. So, IMHO

[O] Bug: Messaging when moving in the agenda [7.9.2 (7.9.2-GNU-Emacs-24-3 @ /usr/share/emacs/24.2.50/lisp/org/)]

2012-10-31 Thread Michael Heerdegen
-from-is-user-regexp \\Michael Heerdegen\\ org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-babel-pre-tangle-hook '(save-buffer) org-mode-hook '((lambda (rest --cl-rest

[O] bug#11042: 24.0.94; dangerous org manual: parse-time-months and parse-time-weekdays

2012-03-21 Thread Michael Heerdegen
Bastien b...@altern.org writes: Hi Michael, Michael Heerdegen michael_heerde...@web.de writes: The org-mode manual under the node The date/time prompt tells: [...] The function understands English month and weekday abbreviations. If you want to use unabbreviated names

[O] Bug: `org-show-context' doc string [7.5]

2011-09-28 Thread Michael Heerdegen
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.

[O] Bug: org-export-html-protect-char-alist type def [7.5]

2011-03-31 Thread Michael Heerdegen
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.