Tim Cross writes:
> I've also learnt to be quite ruthless in making decisions about what to
> archive and what to simply delete. This is possibly the hardest
> behaviour to learn. In a digital age, it is way too easy to keep
> everything. However, this has a hidden cost - the quality of material
Ihor Radchenko writes:
> Samuel Wales writes:
>
>> one issue with this great thing called capture is that there is
>> nothing quite so convenient that does the exact opposite.
>>
>> [you can regularly purge, if your life/forest is simple enough or you
>> have the physical ability to do
Samuel Wales writes:
> one issue with this great thing called capture is that there is
> nothing quite so convenient that does the exact opposite.
>
> [you can regularly purge, if your life/forest is simple enough or you
> have the physical ability to do things. but you can't just
>
===
Hmm... I myself went through several refactors of my Org file
structures. Exactly because things become unmaintainable over time. It
is hard to design a good structure without enough experience with the
old one.
===
[my forest structure is actually pretty good. it is partly that i
ahve more
well, i implied it at least.
On 12/20/21, Samuel Wales wrote:
> more below.
>
> On 12/20/21, Ihor Radchenko wrote:
>> If more people are interested, I do not see why next-error integration
>> cannot be included into Org.
>
> nitpick: it already is integrated for sparse tree matches in the
>
more below.
On 12/20/21, Ihor Radchenko wrote:
> If more people are interested, I do not see why next-error integration
> cannot be included into Org.
nitpick: it already is integrated for sparse tree matches in the
outline. i suggested that if next-error worked for more things, like
agenda
Samuel Wales writes:
> On 12/19/21, Ihor Radchenko wrote:
>> multiple agenda views is not an uncommon workflow. You may have daily
>
> i think this is a strong objection. multiple simultaneous agenda
> views seems to sink my suggestion.
>
> can one have multiple simultaneous c-c / buffers?
manual> These
commands can also be used in ‘*grep*’ buffers, where the hyperlinks are
search matches rather than error messages (*note Grep Searching::).
--- (info "(emacs) Compilation Mode")
it is likely common to have grep and compilation mode open at the same
time. i think this is like your
[as an example, i should not have brought up the follow mode example
at all. it seems to have only confused readers. i was trying to
forestall any suggestions that follow-mode exists and can do the job
that next-error can is all. it can't do the same job.]
On 12/19/21, Samuel Wales wrote:
>
On 12/19/21, Ihor Radchenko wrote:
> multiple agenda views is not an uncommon workflow. You may have daily
i think this is a strong objection. multiple simultaneous agenda
views seems to sink my suggestion.
can one have multiple simultaneous c-c / buffers? and multiple
grep/occur/compilation
Samuel Wales writes:
> btw, if anybody has difficulty understanding why i mention a bug or
> suggest a feature [such as why anbydoy would want it], please feel
> free to say so, otherwise i don't know that that is the case. [please
> go easy on me though.]
This is a difficult query. There are
another thing: it is an org consistency fr also, as in the outline c-c
/ does use next-match, and it would be good to have the same
capability among agenda results files, not merely in a single buffer.
On 12/18/21, Samuel Wales wrote:
> btw, if anybody has difficulty understanding why i mention
btw, if anybody has difficulty understanding why i mention a bug or
suggest a feature [such as why anbydoy would want it], please feel
free to say so, otherwise i don't know that that is the case. [please
go easy on me though.]
in this case, it is an emacs consistency fr. across emacs,
Samuel Wales writes:
> just curious whehter fr/bug/inconsistency emails drop off the end of
> the org mailing list or whether they go on a todo list someplace.
Yes and no. Most of your emails are feature requests (at least that's my
impression) and some of them are very short and do not explain
just curious whehter fr/bug/inconsistency emails drop off the end of
the org mailing list or whether they go on a todo list someplace.
i have others not responded to but can't keep track of them, but
that's ok. i am grateful for the work done on org. i realize this is
not a hight priority item,
if you search for a regexp in a single org buffer, you can do
next-error to go to the next search.
if you search in agenda, there is a mode where the match will show up
in the ohter window. i find this inconvenient.
there is no next-error to go to the next match for agenda searches.
or am i
16 matches
Mail list logo
