From: Samuel Wales <firstname.lastname@example.org> To: email@example.com Subject: Re: next-error for agenda searches Date: Sat, 18 Dec 2021 18:10:21 -0700 [thread overview] Message-ID: <CAJcAo8tyEWyaqT3YnrVQsnKCuwpwpbsk335++--tASw_gSjN+Q@mail.gmail.com> (raw) In-Reply-To: <CAJcAo8sbpBqSvkLF5ByhXxOvc-K--39_JNd-n2k47=hkNXVbug@mail.gmail.com> 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-error goes from match to match, and it seems to me [perhaps i am mistaken] that agenda searches should be emacsy too. as for why it would be useful to me, so that i can get full context, with point at the match, thus 1] getting all the matches in my hands in the outline and 2] being able to edit immediately. 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]. 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. but i think it is an emacs consistency issue. i agree with the frequently expressed idea that new features should be justified carefully, and next-error working as in e.g. grep seems right here. 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. 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. :] On 12/14/21, Samuel Wales <firstname.lastname@example.org> wrote: > 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 missing this feature someplace? seems strange not to? > > such a thing would be consistent with c-c / / in an org buffer, > grep-mode, occur-mode, compilation-shell-minor-mode. thanks! > > -- > The Kafka Pandemic > > A blog about science, health, human rights, and misopathy: > https://thekafkapandemic.blogspot.com > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2021-12-19 1:11 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 [this message] 2021-12-19 1:14 ` Samuel Wales 2021-12-19 13:31 ` Ihor Radchenko 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=CAJcAo8tyEWyaqT3YnrVQsnKCuwpwpbsk335++--tASw_gSjN+Q@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --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).