My approach is simple. For TODO items, I archive to separate file when
done. That file is easily searchable, e.g. using C-c /.
I keep both the original file and the archive file under revision
control, just in case.
> The issue (I think) is, when you mark the TODO as DONE, you lose the
> info o
On 2021-02-26 01:20, Kyle Meyer wrote:
TRS-80 writes:
On 2021-02-24 15:58, TRS-80 wrote:
On 2021-02-16 23:30, Kyle Meyer wrote:
[...]
So, if I'm reading your preferences correctly, it sounds like you
want
just the first suggestion in the above snippet, leaving
org-adapt-indentation at its d
On 2021-02-26 01:22, David Masterson wrote:
There are many ways of maintaining history in a group of Org files:
1. Archive within a file
2. Archive to a separate (archive) file
3. Special TODO types for history
4. Special TAG types for history
5. etc.
My question is, if you have meetings/phone c
On 2021-02-25 15:49, Florian Lindner wrote:
Am 25.02.21 um 21:22 schrieb Florian Lindner:
is this possible with org-mode? Given a tree:
* Name
:PROPERTIES:
:ARCHIVE: ???
:END:
** Archive :ARCHIVE:
** Some node
Upon archiving "Some node" (or any direct or indirect sub-node of
Projectname) I
Priority cookies are always in a headline.
The attached patch speeds up fontification of a 1k lines buffer by 0.1
second.
Note that the variable org-priority-regexp can't be modified since
it is used in the agenda and in org-get-priority.
Regards,
--
Sébastien Miquel
>From a348a3834b79608a20bf
org does indeed have a lot of related features, maybe too many even.
here is some of what i do.
- if i doneify, it means i will likely not need to search for it.
archived to a file.
[currently the archiver is so slow i can't use it]
CLOSED: [2012-11-08 Thu 19:40]
- state logging for repeaters
Ihor Radchenko writes:
> David Masterson writes:
>> My question is, if you have meetings/phone calls as TODOs, what is the
>> preferred way to handle when they move into history so that, *much*
>> later, you can easily produce a list of all of the meetings/phone calls
>> with dates and times of
Tim Cross writes:
> David Masterson writes:
>
>> There are many ways of maintaining history in a group of Org files:
>> 1. Archive within a file
>> 2. Archive to a separate (archive) file
>> 3. Special TODO types for history
>> 4. Special TAG types for history
>> 5. etc.
>>
>> My question is, if
Eric S Fraga writes:
> My approach is simple. For TODO items, I archive to separate file when
> done. That file is easily searchable, e.g. using C-c /.
Ah! org-occur! That's something forgot about and looks useful.
> I keep both the original file and the archive file under revision
> control,
David Masterson writes:
> Tim Cross writes:
>
>> David Masterson writes:
>>
>> For me, my TODOs are setup so that they record a date stamp for when
>> they were added and whenever they change state e.g. started, done,
>> delegated etc.
>
> So, you use progress logging.
Yes.
>
>> For non-TOD
it is neither raw yank behavior nor org syntax
in recent maint
i have org-yank-adjusted-subtrees t
* org-yank is funny
*** kill this line (with newline) then try yanking at ^ places (remove
the ^ first)
the fault lies in the stars
insertion above and arbitrary demotion
*** x
asdfnaksdj fnkadsn f
*** kill any header (with newline) then try yanking in various places
in the stars of any indented header that has things above it. you
should get multiple demotions that do not conform to outline.
On 2/26/21, Samuel Wales wrote:
> it is neither raw yank behavior nor org syntax
>
> in recent mai
Tim Cross writes:
> David Masterson writes:
>
>> What would you use to then make a list of all meetings you had last year?
>
> For me, archiving is about data I'm unlikely to need again, but just in
> case I do, it is in the archive. I rarely look at my archives. However,
> when I do archive, I
note that there is an issue when you try to name your archive files
using years like computer-2000.org_archive. it can take seconds to
find-file big files so it is understandable to want to name files like
that.
however, if you change the name of an archive file, it will not be
found by org when
David Masterson writes:
> Interesting, but then how do you get the list? I mean is there an
> agenda to use?
Generally yes, you can use agenda. Or you can use sparse tree (more manual).
For agenda, if you customise org-log-done, you can use
org-agenda-log-mode ("v l" or "v L" in an agenda buffe
Samuel Wales writes:
> perhaps also changing org-archive-file-header-format to allow a format
> thingie for a timestamp would allow you to take parts of an archive
> file and move them into one per year without having to put the date in
> each archived entry.
FYI: I have implemented automatic pe
Samuel Wales writes:
> [currently the archiver is so slow i can't use it]
Are your existing archives very big (few Mbs)? If so, you may try to
speed up the archiving using feature/org-fold branch [1]. If that is not
enough, I recommend splitting archives on yearly basis [2] or disabling
font-lo
17 matches
Mail list logo
