ts (and then debug/maintain that code).
Change it in the compose menu then.
That's what other MUAs do, too.
You can even use macros for predefined addresses for "one-click"
changes, even less hassle than with your $ask_from.
--
? Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
some
> message in some mailbox, instead of attaching the whole message
> (except by copying them first)?
When in compose menu, see '?' search for "attach", maybe one of the
hits is what you want.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effor
said something about changing a function for
wrapping/ padding/ format-flowed which applied for From_, too.
b) diff the source before and after the fix.
c) ChangeLog should tell you, too.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude
ted it today. :-)
Rocco said he fixed it in the repo, I haven't recompiled nightlies
since then.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
gt; That's it! Thanks! Plus the double quotes ...
>
> save-hook '~s "RC\\(ci\\): \\[string\\]"' =bla
See also 'PatternQuoting' on the mutt-wiki.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
it would hurt normally, but not quite the intention, is it?
If you have low Timeout and big ImapKeepAlive, it would be called
very often, maybe too much for slow lines?
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
t are the real name of an option) have a link
> to the real definition. Would that be sufficient?
How about putting a list toc directly behind the toc?
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
e various
> commands don't each get their own subsection, they're just part of
> a list (and thus don't show up in the ToC). It seems to me that if
> this is appropriate for the long list of config *commands*, the
> same would be appropriate for config *options*.
>
> A
attachement.
Hook yourself into ticket #2893 for updates.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
t puts _both_ addrs in the To:.
desired:
- put/ use only List-Post: addr, unless MFT set and honoured.
questions:
- is the old or new way desirable?
- why? (my reason is the current is unexpected)
- could this be turned off, generally or by option?
--
© Rado S. -- You must provide YOUR effor
feature would allow for 1-click solution (beware of the
amazon patent), but Gary's does that already with the current code.
As always the struggle between adapting the code or the own setup to
suit convenience...
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
t; > the list if the message is to a subscribed list, or to have a
> > different command for "compose to list".
>
> Why isn't list-reply close enough for that?
Because you don't want to reply to an existing thread but start a
new one.
I have aliases for that. ;)
--
F2=$(echo $line|cut -d$FS -f2)
> F3=$(echo $line|cut -d$FS -f3)
> /usr/bin/mutt -s " " $F1 -i " " [body file text to include] -a " " $F2 "
> " $F3
> done < $FILE
>
> When running "test2" I have various errors but to cut
jump back to "bind" to redefine it.
What is "command-line mode"?
BTW, this is rather for mutt-users than mutt-dev.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
mp;& !h->read));
> case M_READ:
make this line:
> + return ((pat->not ^ h->replied) || (pat->not ^ h->grouped));
rather like this:
> + return (pat->not ^ (h->replied || h->grouped));
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
re I
must + can delve into the depths of IMAP. ;)
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
diff -ru mutt-1.5.17/copy.c mgo/copy.c
--- mutt-1.5.17/copy.c Tue Apr 10
=- Cameron Simpson wrote on Tue 3.Jul'07 at 21:06:18 +1000 -=
> On 26Jun2007 20:43, Rado S <[EMAIL PROTECTED]> wrote:
> | All you need to know about a link is that it is a link,
> | while anything else is more interesting from the destination.
>
> Generally speaking,
=- Daniel Jacobowitz wrote on Mon 25.Jun'07 at 12:56:41 -0400 -=
> On Mon, Jun 25, 2007 at 05:57:45PM +0200, Rado S wrote:
> > =- Daniel Jacobowitz wrote on Sun 24.Jun'07 at 21:46:44 -0400 -=
> >
> > > On Sun, Jun 24, 2007 at 05:55:39PM +0200, Rado S wrote:
=- Daniel Jacobowitz wrote on Sun 24.Jun'07 at 21:46:44 -0400 -=
> On Sun, Jun 24, 2007 at 05:55:39PM +0200, Rado S wrote:
> > when sorting folder lists (incl. "mailboxes") by size/time, a
> > symlink is listed with its own time/size rather than the file's it
Moin,
when sorting folder lists (incl. "mailboxes") by size/time, a
symlink is listed with its own time/size rather than the file's it
is pointing to, which is not so useful. The attached patch keeps the
flag for the link but replaces time/size with that of the file.
--
© Rado
-encoding. Once mutt supports that, too, we can change
it back.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
r than a
default (which might be the same as your default so you can't notice)?
Use a completely different addr from the alternates as your default.
If that is the case, then you must pay attention to tag'em in the
right order.
--
© Rado S. -- You must provide YOUR effort for your goal!
latively small oldies group, neglecting the
possibilty that generally always a new stability could be reached
once a new default matures to "established".
You're mistaken that I don't value stability, au contraire.
I just value corrections of bad decisions even more! :)
Bad hab
aults offered and
having everything set up for it already, just waiting to go.
(people not having setup mailboxes can't use it by default
either yet: "next" relative to what list? Nothing happens/ differs
from "normal" change-folder)
> Reaching the consensus on Usenet:
both the /unbind all/ and /rebind to
> generic/ new capabilities. My humble is that both features are
> dearly wanted, but that the syntax should be better integrated
> with the only current /unbind to unbound/ syntax (bind "noop"
> keyword). Tamo-san made a patch doing tha
future cases as well as localized
deviations where the noise is sent (err-out) will be taken care of.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
=- Luciano Rocha wrote on Wed 23.May'07 at 18:48:01 +0100 -=
> when using `which` send errors to /dev/null
> {...}
> -if test -x "`which md5`"
> +if test -x "`which md5 2> /dev/null`"
On solaris 8 which produces noise on STDOUT, not STDERR.
Maybe the a
e of what you do?
> For what benefit? None. This doesn't even reduce the lenght of
> , only pushes those unbound functions to the end of list.
Heh... this _is_ the benefit, since people read top-down, so they
have less to scroll down.
> > Then, when mutters are ready to use it
undancy between run-time functions and cmd-line options is
another matter again, but not so much of a conflict, since options
are optional and therefore don't stand in the way by default.
> >> Slrn has and
> >
> > More equivalent were if it had {...}
>
> Come
his doesn't mean it can't get back on track with
some effort and help from above.
If we don't give a damn (hi Dave ;) things just get worse while we
could do something about it. Mutters won't jump off mutt, they're
flexible and (can) adapt when informed ahead of time.
> > sorry Alain, I don't expect this to be the "new way" for
> > changing mailboxes, priorized mailboxes are too useful ;)
>
> Priorized mailboxes indeed are very usefull, to you and many
> others. However some people don't value priorized mailboxes so
> much, or not at all. I said "some amount of", not "all" users. I
> never intended to replace
> , but to be aside.
I haven't understood it that way, but see them both on par.
I was just opposing the idea that because "it will be so hype" it
_deserves_ a separate function.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
I'm sorry for the noise, Alain, I fired off before noticing reponses
in #mutt explaining what it really does. ;-/
=- Gary Johnson wrote on Wed 9.May'07 at 12:22:31 -0700 -=
> On 2007-05-09, Rado S <[EMAIL PROTECTED]> wrote:
> > I admit, I haven't follow
bound to comma, manual too. But the
> comma key gives nothing. Nothing, until user presses the next key.
> This is much more annoying.
Uh, if the user messes around with bindings, he's no beginner
anymore and should RTFM and undertstand which effects his changes
have, in this case overridi
und it was not trivial
(at least for me), and then it was pushed down on the todo list by
other things. ;)
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
.
> BTW, in Mutt's speak this function doesn't jump to the next
> _folder_, but to the next _mailbox_ (a folder declared in
> "mailboxes" list) with new mail. Nuance. Shouldn't it better read:
> "open next mailbox with new mail"?
+1
There are some mo
t; for, or why "dellines-=3;").
If I know what happens there, then I could make %l + %L match _and_
make those vsize functions faster by dropping all the extra
calculations to include the header size at those other places.
Is "size + vsize" calculation in copy.c needed at all
=- Lars Hecking wrote on Mon 30.Apr'07 at 10:19:44 +0100 -=
> This is still broken as of 1.5.15. Is there something like a
> nightly snapshot I can download? I haven't really worked with
> mercurial yet.
http://dev.mutt.org/nightlies/
--
© Rado S. -- You must provide YOUR e
ebug, then give advice (how) to get it.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
--- morg/main.c Wed Apr 11 09:00:10 2007
+++ mgo/main.c Sat Apr 14 16:24:25
#x27;A' as IMAP-introducer key, and then 1 per IMAP-server,
like Aw, Ar, Ai, ... -> imaps://.../
and then you can add whatever you want manually, incl.
tab-browsing as Brendan has described.
Oh, and can we please adjust the subject to better get an idea
what a sub-thread is about? Thanks. :)
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
normal
mutt world. Don't dare to send /alternative somewhere else. ;)
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.
HTML eMail
per se, just the need to have specific mutt-code support for sending
/alternative, when it already can be achieved with some teaking.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.
g here.
What do _you_ do with the _HTML part_ of the eMail?
Really just resend it back unchanged?!
Don't people have "sent" folders?
("but what about the context?" you might ask: tag-forward it to
those requesting it _when_ they do so, or do they really check
the whole
please ask whether you may add him
on his behalf. Don't add people who don't agree to be listed.
(Steve, pdmef, Michael: I hope you don't mind that I added you as
examples, otherwise I'll remove you again ;)
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort
tachment multipart/mixed,
why does it have to be /alternative?
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.
Let them have their way, why do _you_ (or mutt) have to (be able
to) send HTML?
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.
y makes progress on the plug-in front.
Let's see what comes out of it.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.
=- Brendan Cully wrote on Thu 22.Feb'07 at 9:30:33 -0800 -=
> On my list at the moment:
> I'll probably apply my ESMTP patch (*dons flame suit*)
> And I think the configurable umask patch is handy.
A FAQ is "attach_dir" for where attachments should be saved.
--
;fix" is to drop the warning.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.
diff -ru org/pgp.c cvs-2/pgp.c
--- org/pgp.c Tue Nov 22 13:31:58 2005
+++ cvs-2/pgp.c Wed
1:00:01 2006
+++ cvs-2/color.c Sat Feb 3 14:26:45 2007
@@ -515,7 +515,7 @@
else
{
int r;
-char buf[STRING];
+char buf[LONG_STRING];
tmp = mutt_new_color_line ();
if (is_index)
--- QUOTE END ---
--
© Rado S. -- You must provide YOUR effort for your goa
ew "secure file creation" mechanism,
which leaves those temp-dirs behind on NFS. See #2707
A temp-fix is to replace the "safe_open" with "open" in lib.c: 622
- if ((fd = safe_open (path, flags)) < 0)
+ if ((fd = open (path, flags,0600)) < 0)
BTW, Lars, can you ha
for that FLAG should reveal not
too many places where it plays a role and perhaps you understand.
Also check the archive, I vaguely remember this has been discussed
some months ago.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your at
some context quote to this new addr.
Thank you and I'm sorry for the noise.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL of it: you get what you give.
51 matches
Mail list logo
