Benchmark-Perl-Formance-Cargo
view release on metacpan or search on metacpan
share/SpamAssassin/easy_ham_2/00006.654c4ec7c059531accf388a807064363 view on Meta::CPAN
color in the ftoc.
> > I also find that I tend to have a bunch of sequences that only ever occur
> > in one folder (some I had forgotten I ever created). So in addition to
> > the "sequences to always show" and "sequences to never show", a
> > preference to only show sequences that occur in more than one folder
> > would be useful, and then have the sequences that occor only in the
> > folder I'm visiting appear in the list when that folder is current.
> > This is just to keep the list size somewhat manageable while remaining
> > productive (I quite often use a sequence to remember a particular message
> > in a folder - the name is used only there, and only for one message,
> > it gives me a handle on the message which remains as the folder is
> > packed, sorted, etc).
hmmm, let me think about it.
> > I haven't updated my exmh for some time now, so I'm not sure if this
> > next one is new, or just new since 2.5, but the Sequences menu (on the
> > bar with New Flist Search ...) only contains "unseen" and "urgent".
> > It would be useful if it contained all of the sequences that the folder
> > happens to have defined. A "New sequence" entry would also be useful
> > (to mark the message with a sequence name that didn't previously exist,
> > which can be done now using "Search" and the pick interface, but is
> > clumsy that way)
The only sequences that are defined there are sequences which are defined in
app-defaults-color or ~/exmh/exmh-defaults-color. I've been thinking about
how to dynamically generate highlighting for other sequences, but haven't got
that figured out yet.
> > Actually, you once could, now when I try this, entering a sequence name
> > in the pick box, and a single message number, or a range N-N in the
> > list of messages, and no pick attributes at all, I now get ...
> >
> > syntax error in expression "int(1+1+(1 hit-1)*(3868-1-2)/(4878-1))"
> > while executing
> > "expr int($minlineno+1+($msgid-$minmsgid)*($maxlineno-$minlineno-2)/($max
> ms
> > gid-$minmsgid))"
> > (procedure "Ftoc_FindMsg" line 46)
> > invoked from within
> > "Ftoc_FindMsg $msg"
> > (procedure "Ftoc_FindMsgs" line 5)
> > invoked from within
> > "Ftoc_FindMsgs $msgids"
> > (procedure "Ftoc_PickMsgs" line 5)
> > invoked from within
> > "Ftoc_PickMsgs $pick(ids) $pick(addtosel)"
> > (procedure "PickInner" line 13)
> > invoked from within
> > "PickInner {exec pick +inbox -list} {4852 -sequence mercury}"
> > ("uplevel" body line 1)
> > invoked from within
> > "uplevel #0 $cmd"
> > (procedure "busyCursorInner" line 8)
> > invoked from within
> > "busyCursorInner $cmd $widgets"
> > (procedure "busyCursorHack" line 32)
> > invoked from within
> > "busyCursorHack $args"
> > ("cursor" arm line 1)
> > invoked from within
> > "switch $busy(style) {
> > icon {busyIcon $args}
> > cursorAll {busyCursor $args}
> > cursor {busyCursorHack $args}
> > default {eval $args}
> > }"
> > (procedure "busy" line 3)
> > invoked from within
> > "busy PickInner $cmd $msgs"
> > (procedure "Pick_It" line 51)
> > invoked from within
> > "Pick_It"
> > invoked from within
> > ".pick.but.pick invoke"
> > ("uplevel" body line 1)
> > invoked from within
> > "uplevel #0 [list $w invoke]"
> > (procedure "tkButtonUp" line 7)
> > invoked from within
> > "tkButtonUp .pick.but.pick
> > "
> > (command bound to event)
> >
> > It has been ages since I did this last though. I tried adding a Subject
> > to pick on (easy as I know what's in the message...) which made no differ
> en
> > ce.
> > Looks as if something is now saying "1 hit" when before it didn't, or
> > similar.
hmmm, that may or may not be my fault...I'll take a look at it.
> > | I've also changed the ftoc colorization as discussed briefly on the l
> is
> > t a
> > | week or so ago.
> >
> > Any chance of making the current message a little brighter background?
> > Just to make it stand out a fraction more than it does (maybe this is
> > more apparent to me than many, as I use very small fonts everywhere,
> > the background of the ftoc line isn't very wide).
I don't see any reason why not. Experiment and let me know what works for you.
Chris
--
Chris Garrigues http://www.DeepEddy.Com/~cwg/
virCIO http://www.virCIO.Com
716 Congress, Suite 200
Austin, TX 78701 +1 512 374 0500
World War III: The Wrong-Doers Vs. the Evil-Doers.
--==_Exmh_1141066573P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.2_20000822 06/23/2000
( run in 2.003 seconds using v1.01-cache-2.11-cpan-364913b4093 )