From: Ihor Radchenko <yantar92@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: next-error for agenda searches
Date: Sun, 19 Dec 2021 21:31:07 +0800 [thread overview]
Message-ID: <87y24graas.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8tyEWyaqT3YnrVQsnKCuwpwpbsk335++--tASw_gSjN+Q@mail.gmail.com>
Samuel Wales <samologist@gmail.com> 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 many emails coming through mailing
lists daily and people tend to skip everything
confusing/unclear/uninteresting. So, difficulty in understanding most
likely leads to no replies.
> in this case, it is an emacs consistency fr. across emacs, next-error
> goes from match to match, and it seems to me [perhaps i am mistaken]
> that agenda searches should be emacsy too.
FYI, I never used next-error. Reading through the docstring, it looks
like it is not very suitable for agendas.
AFAIU, normal use case of next-error is when you have a big project with
multiple files and you want to look at the context for every compiler
error. You have a single compiler error log that can be assigned to
places in the project.
This kind of assumption is not correct for Org agendas. I assume that
your workflow only includes a single agenda view all the time. However,
multiple agenda views is not an uncommon workflow. You may have daily
agenda, some tag-matching agendas, agendas with various restrictions,
etc. It would be unclear which agenda view to use when you call
next-error. Last generated? Last visited? What about agenda filters?
Dimmed tasks?
> furthermore, the next-closest thing, follow mode, puts point in wrong
> window. also, 'canonical visibility is not present so i cannot see
> everything [this might or might not be fixable by user].
Can you elaborate?
> also there is an accessibility issue with it. i use large fonts so 2
> windows do not show much. i use 2 windows only for very rare
> completion or selecting purposes. not usable here.
I also use relatively large fonts, though I do have space for two
windows (but not more). Note that there is org-agenda-entry-text-mode.
Might be useful. Also, I personally prefer org-quickpeek in agenda.
> this isn't a huge deal for me at all, but e.g. when i do agenda
> searches i get really overwhelmed by the size and irrelevance
> [including duplication] of my own org forest developed over years.
This sounds like you could use more tight search criteria or custom
agenda searches. An example of irrelevant vs. relevant information could
help us to suggest something for you.
> next-error would help me traverse and trim it rapidly. i could
> perhaps create a kb macro to emulate it, but i haven't tried yet.
> then again, one could do so for grep mode etc. also. :]
If you decide to go with macro, it should not be too hard. Just <RET> on
agenda item, do your edits, macro-beg, switch to agenda buffer,
next-line, <RET>, macro-end
Best,
Ihor
next prev parent reply other threads:[~2021-12-19 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 1:34 Samuel Wales
2021-12-18 8:44 ` Samuel Wales
2021-12-18 10:09 ` Ihor Radchenko
2021-12-19 1:10 ` Samuel Wales
2021-12-19 1:14 ` Samuel Wales
2021-12-19 13:31 ` Ihor Radchenko [this message]
2021-12-20 1:45 ` Samuel Wales
2021-12-20 1:58 ` Samuel Wales
2021-12-20 2:01 ` Samuel Wales
2021-12-20 14:57 ` Ihor Radchenko
2021-12-20 22:15 ` Samuel Wales
2021-12-20 22:16 ` Samuel Wales
2021-12-24 1:15 ` Samuel Wales
2021-12-24 11:14 ` Dealing with growing backlog (was: next-error for agenda searches) Ihor Radchenko
2021-12-24 11:51 ` Tim Cross
2022-05-15 7:22 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y24graas.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
--subject='Re: next-error for agenda searches' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).