Hi. I have started this instance of GNU Emacs 25.1.91.1 with an empty init
file and then I customized org-log-note-clock-out to t. Then I created a
new Org buffer with a single level 1 headline, and set property
CLOCK_INTO_DRAWER to nil. I then clocked in and then out, adding a note.
The note
On 3 February 2017 at 20:01, Nicolas Goaziou wrote:
> The fix for the other issue you reported about CLOCK and notes probably
> has also fixed this one. Could you confirm it?
According to my very brief test, yes it fixed.
Thank you!
--
• I am Brazilian. I hope my
Hi. I wanted to temporarily run git Org so I could test a fix by Nicolas
Goaziou. I have pulled the master branch and adapted local.mk. In that
file, I set:
prefix = ~/.emacs.d/locally_built_org
# Where local lisp files go.
# $(prefix)/emacs/site-lisp/org
lispdir=
Hi.
In log mode, after each clock line the agenda should show the corresponding
clock note. Instead, it shows the clock note for the previous clock line.
For example, with the entry
*** Espe2016 exp
:PROPERTIES:
:CREATED: [2017-01-27 Sex 16:50]
:CATEGORY: ponto exp
On 10 February 2017 at 11:53, Bastien wrote:
> Org 9.0.5, a minor bugfix release, is out.
In Org 9.0.5, clock out notes are again stored below the corresponding
clock line, restoring the behavior of an earlier release. There were
interim releases, up to 9.0.4, that stored the clock
Hi. I have set appt-message-warning-time to 10. However, there are two
files where I would like the warning time to be 0. Is there a quick way to
do it? Which? I do not want to add APPT_WARNTIME properties to each entry
because, if I did that, then:
1. Every time I added a new entry to one of
1. Write a file named agenda_bug.org with the following content
(remove indentation):
*** TODO Dummy
SCHEDULED: <2017-03-06 Seg> DEADLINE: <2017-03-07 Ter ++1m -6d>
2. Start GNU Emacs 25.2.1 (25.2-rc2) with an empty init.el.
3. (require 'org-agenda)
4. Customize
On 5 October 2016 at 19:24, Nicolas Goaziou wrote:
> You gave a recipe to reproduce the example. I was being lazy and
> expected the complete (final) example. Anyway, I did my homework.
>
> This should be fixed: the message is slightly less frightening now.
>
> Regards,
On 5 October 2016 at 06:44, Nicolas Goaziou wrote:
>
> OOC, could you show the footnote section triggering this warning? Org
> Lint ignores property drawers there (i.e., it shouldn't raise an error),
> so I'm wondering how is inserted this timestamp.
I don't understand.
Hi. In most of my Emacs files, I set any file local variables using a local
variables list near the end of the file. However I just realized a pitfall.
Emacs, according to its manual, only recognizes this local variables list if
its location fulfills two criteria:
1. It starts no more than 3000
Finally the second batch I promised. Sorry for having taken this long.
- org-table-convert-region docstring is less complete than the manual\\
The docstring contains the line:
#+BEGIN_QUOTE
integer When a number, use that many spaces as field separator
#+END_QUOTE
I have some observations about your fixes:
1. Tag keys (for fast selection)
1) When clarifying that tag keys are case-sensitive letters, we
forgot to adjust
org-tag-persistent-alist’s docstring. Please adjust it.
2) And now that I think of it, is it appropriate to write "a-zA-Z" in
On 11 November 2016 at 22:47, Nicolas Goaziou wrote:
> `org-tag-persistent-alist' is about "characters". I think it is clear
> that characters are case-sensitive already.
Currently, the docstring of org-tag-alist says "SELECT is a case-sensitive
letter" and the docstring
On 8 December 2016 at 04:44, Carsten Dominik wrote:
> One additional point is, of course, that org-depend is not part of the core,
> but was written as a proof of concept. Is anyone besides Karl using it
> regularly? I don't want to break anything by changing it.
I use it (in a
On 9 December 2016 at 21:31, Nicolas Goaziou wrote:
>> I set them up as org-habit habits for the following desirable features:
>> - Only show on the agenda for today, not for other days.
>> - Appear at the end of the agenda for today.
>> - Hide when I type K.
>
> What
On 8 December 2016 at 08:16, Jorge Morais Neto <jorge13...@gmail.com> wrote:
> On 8 December 2016 at 04:44, Carsten Dominik <domi...@uva.nl> wrote:
>> One additional point is, of course, that org-depend is not part of the core,
>> but was written as a proof of conce
On 3 January 2017 at 14:16, Nicolas Goaziou wrote:
> I cannot reproduce it with, e.g.
>
> * TODO test
> :PROPERTIES:
> :Effort: 2:00
> :END:
>
> and a bare configuration. Could you double-check you're really using Org
> 9.0.3?
I reproduce it (the behavior and the
On 9 March 2017 at 14:17, Eric Abrahamsen wrote:
> You're probably looking for the `org-log-reschedule' option: that will
> let you leave a stamp or take a note if you change the scheduled date of
> an option.
>
> I know that would end up doubling the size of my org
On 5 March 2017 at 15:03, Nicolas Goaziou wrote:
> It has an effect, but you are enforcing a pre-warning delay of 6 days.
> in the time stamp above.
>
> I think local syntax overrides global settings. IOW, I don't think this
> qualifies as a bug.
It would have been useful
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 mailing list.
On 29 June 2017 at 17:11, Jorge Morais Neto <jorge13...@gmail.com> wrote:
> In two days this is the second time Org loses a TODO state change note
> draft. I guess that, if I realize the note will take time to compose, I
> am supposed to compose it in some file and, only w
On 1 July 2017 at 13:58, Nicolas Goaziou wrote:
> Even if the window configuration is lost, I cannot see how the "*Org
> Note*" buffer could be closed. Are you certain it was not accessible
> anymore from the buffer list?
I do not remember and unfortunately I do not have
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 mailing list.
How about a diary-style sexp entry, with org-class? That is, something
like ~<%%(org-class 2017 7 31 2018 3 23 1)>~. That example would appear
on the agenda on every Monday between 2017-07-31 and 2018-03-23.
Regards
--
- I am Brazilian. I hope my English is correct and I welcome feedback
-
[unfortunately the first email went only to Adam Porter; now I address the list]
On 2 September 2017 at 22:10, Adam Porter wrote:
> Thanks for sharing that, I didn't even remember org-expiry. Very clever
> use of it! You seem to know more about elisp than you give yourself
>
On 31 August 2017 at 08:55, Tim Visher wrote:
> I would like to track the time I created a tree and the last time it was
> edited, like ctime and mtime on a filesystem. Is that possible to have
> happen automatically?
To insert a creation timestamp I use org-expiry. I have
The mentioned manual section says:
`C-c C-c or C-c C-x C-u (`org-dblock-update')'
Update dynamic block at point. The cursor needs to be in the
`#+BEGIN' line of the dynamic block.
However, the docstring only says
User command for updating dynamic blocks.
On 3 November 2017 at 12:11, Anders Johansson wrote:
> I use org-id and got some surprising reports of duplicate IDs. It seems that
> the issue is that one of my files containing IDs has a filename consisting
> of some non-ascii characters (a Swedish ä).
This may be
On 25 October 2017 at 12:04, Alex Branham wrote:
> Whenever I ediff an org file, the three windows start with the content folded
> and out of site. I have to navigate to windows A, B, and C and hit S-
> until everything is visible. Does anyone know a way to start org
29 matches
Mail list logo