===
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 s
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
> outl
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 tex
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? and
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 mu
[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
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 s
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 m
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 a
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, next-erro
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,
12 matches
Mail list logo
