emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: many an agenda keyword search improvement
Date: Mon, 29 Mar 2010 20:05:53 -0700	[thread overview]
Message-ID: <20524da71003292005k5260b8e2k44ac440610a97df1@mail.gmail.com> (raw)
In-Reply-To: <FDF006AB-67FB-4240-A6A0-58D978448743@gmail.com>

On 2010-03-29, Carsten Dominik <carsten.dominik@gmail.com> wrote:
> Hi Samuel,
>
> thanks for this message.  I have put this on my list, but
> I cannot see when I will be able to work on this.

Ah, I overwhelmed you.  :)

Anybody else find them interesting?  :)

Thanks for all of your work on org-mode.

As always.

Samuel



> - Carsten
>
> On Mar 13, 2010, at 6:36 PM, Samuel Wales wrote:
>
>> Here are agenda suggestions for org keyword searches that I
>> have been collecting.
>>
>> All of them would be very useful (to me).
>>
>> Is it better to use separate emails?
>>
>>
>> 1.  Colorize headlines as in the outline.
>>
>> When I search for "forums" in org using M-x
>> org-agenda-dispatch s, I get an agenda that does not
>> colorize the italic part of the headline below.
>>
>> * NAKA [#A] /email and forum/
>> forums                             :now:refile:
>>
>> If it could be colorized normally, I would be able to find
>> the headline much faster.
>>
>> 2.  Colorize matches.
>>
>> Some hits are from headlines (i.e. "forums" is in the
>> headline), but others are from body text.  These are not
>> distinguished.  Also, regexp searches do not show what
>> matched, and you can't tell where the match is in a headline
>> easily.
>>
>> These problems are solved by colorizing matches (e.g. using
>> the same face that isearch does).
>>
>> 3.  Pre-seed isearch and isearch-regexp.
>>
>> If you RET on a headline, you sometimes want to search for
>> the search expression (e.g. "forums") in the body text.
>> (Optionally) pre-seeding isearch and isearch-regexp with the
>> search expression would allow you to not have to type it.
>>
>> This would turn the entire expression, such as "alpha beta
>> {gamma\|linoleic}", into a regular expression.
>>
>> 4.  E-like mode for body matches.
>>
>> If matches are in body text, perhaps the matching lines can
>> be shown under the headilnes with the matches highlighted.
>>
>> 5.  Link type for agenda search.
>>
>> Sometimes you want a todo item to do an agenda keyword search.
>>
>> 6.  Colorize matches in other window.
>>
>> When you show the outline buffer in the other window,
>> colorize matches there.
>>
>> 7.  Search within results.
>>
>> The / command is useful for searching for tags within
>> results (including body text) without having to incur the
>> overhead of an entire agenda search again.
>>
>> I'd like the same thing for keyword searches.  Searches are
>> very slow on my system, so I never refine searches.  But I
>> would if I had this capability.
>>
>> 8.  Or search within results and do other stuff.
>>
>> I also have a proposal for an idea that supersedes #7 and
>> also allows more functionality.  I alluded to it in previous
>> email in a footnote.
>>
>> Suppose we could have a "next command operates on the
>> selected entries (or ALL displayed entries if none
>> selected)" command?
>>
>> This could fold the / command and the command I am
>> requesting into a single facility that can then be used for
>> other purposes also.  To do a todo search within a keyword
>> search, you just do the keyword search, run the command,
>> then do a todo search.  Or any other command.
>>
>> It could be on /.  Current / behavior could be done with two
>> /es (first says next command is within results and second
>> says do tag search).
>>
>> 9.  Search in attachments.
>>
>> I have already covered this in another email.  Perhaps the
>> discussion could be revived if there is enough interest.
>>
>>
>> Thanks.
>>
>> Samuel
>>
>> --
>> Q: How many CDC "scientists" does it take to change a lightbulb?
>> A: "You only think it's dark." [CDC has denied a deadly disease for
>> 25 years]
>> ==========
>> Retrovirus: http://www.wpinstitute.org/xmrv/index.html
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> - Carsten
>
>
>
>


-- 
Q: How many CDC "scientists" does it take to change a lightbulb?
A: "You only think it's dark." [CDC has denied a deadly disease for 25 years]
==========
Retrovirus: http://www.wpinstitute.org/xmrv/index.html

      reply	other threads:[~2010-03-30  3:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-13 17:36 many an agenda keyword search improvement Samuel Wales
2010-03-13 23:54 ` Samuel Wales
2010-03-29 10:06 ` Carsten Dominik
2010-03-29 11:28 ` Carsten Dominik
2010-03-30  3:05   ` Samuel Wales [this message]

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=20524da71003292005k5260b8e2k44ac440610a97df1@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).