Ihor Radchenko writes:
> > Though, I think you didn't change the occurrence that this thread
> > started with - `org-eval'. Does changing this one cause problems?
>
> Tests are passing.
> I originally skipped it because it did not look useful from a brief
> glance to have full backtraces there,
Michael Heerdegen writes:
> I reviewed it shortly - looks appropriate.
Though, I think you didn't change the occurrence that this thread
started with - `org-eval'. Does changing this one cause problems?
Michael.
Ihor Radchenko writes:
> I changed instances that appear to be safe.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5b4eebfab
I reviewed it shortly - looks appropriate.
Thank you very much!
Michael.
Ihor Radchenko writes:
> As for condition-case-unless-debug, may you create a patch?
> But please do not replace everything blindly - I know for sure that at
> least some `condition-case' clauses are there on purpose.
I nearly never had a closer look at the org-mode code (other than
blindly).
Ihor Radchenko writes:
> What are those?
> I do not have anything failing on my side.
See the attached file. I had been using an up-to-date Emacs master build.
Michael.
<>
Ihor Radchenko writes:
> In my attempts, the tests started failing for no obvious reason.
> Just from changing `condition-case' to `condition-case-unless-debug'.
>
> Though I did not investigate if it happened for every atomic change.
Hmm - mine gave a different result: I cloned the org-mode
Ihor Radchenko writes:
> This is a good idea, except that `condition-case-unless-debug' has
> non-obvious side effects that interfere with ERT (Org testing system).
What side effects are these?
Thx,
Michael.
Hello again,
> selecting a date from within `org-read-date' from the calendar works
> with mouse-1, but not with mouse-2 (with latest Emacs master and my
> settings loaded at least).
>
> The code seems to intend that it also works with mouse-2, but it fails.
>
> Why it doesn't work? Oh, that's
Michael Heerdegen writes:
> Nothing is lost since the original popup-menu for the calendar is
> still being bound to down-mouse-3 (the more expected key for such a
> menu in my opinion, at least 2021).
That was not quite correct, however. These are the defin
Michael Heerdegen writes:
> So please consider [...]
Oh, and please keep me CC'd, I don't read the list regularly.
Thanks, Michael.
Hello,
selecting a date from within `org-read-date' from the calendar works
with mouse-1, but not with mouse-2 (with latest Emacs master and my
settings loaded at least).
The code seems to intend that it also works with mouse-2, but it fails.
I don't prefer mouse-2, but it would be good to
Ihor Radchenko writes:
> You are right. Since this is hard-coded, you may have to use :around
> advice to disable org-log-setup: [...]
Do you think others may want the same and it could be worth to implement
this feature?
Michael.
Ihor Radchenko writes:
> > Is there a way to get only the :LAST_REPEAT: prop logged, without the
> > ever-growing list?
>
> I guess you can try to play with org-log-done and org-log-repeat
> variables.
Thanks. But as far as I recall, that's what I already tried and it
didn't help.
As far as I
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]
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
>
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:
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
>
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
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
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
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.
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
Hello,
what's the difference between org-marker and org-hd-marker markers?
What does "hd" stand for?
TIA,
Michael.
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
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
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.
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
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:
>
>
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 <%%(...)>,
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)))
>
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
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
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
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
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
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
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
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!
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
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.)
>
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
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
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
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
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,
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
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
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
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
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.
^
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
-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
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
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.
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.
55 matches
Mail list logo
