On Wed, Aug 03, 2022 at 02:37:00PM +0900, Kenichi Asai wrote:
Yes, and it solved the problem!!! Thank you very much!
I haven't compiled mutt by myself for long, so I rewrote the homebrew
formula to use the patch and let homebrew recompile (mutt 2.2.3).
Thank you Kenichi and Dennis for confirm
On Tue, Aug 02, 2022 at 08:55:53PM -0700, Kevin J. McCarthy wrote:
> - while (ISSPACE (*buf))
> + while (is_email_wsp (*buf))
I was also able to reproduce the issue (on macOS) and can also confirm
that with this patch, the issue no longer occurs.
Dennis
o use the patch and let homebrew recompile (mutt 2.2.3).
It's really great that I don't have to check Subject every time any
more to see if the last character is truncated. Thank you Kevin and
all the others for considering and solving this problem.
Sincerely,
--
Kenichi Asai
m: Kevin McCarthy
Date: Tue, 2 Aug 2022 20:51:17 -0700
Subject: [PATCH] wip: testing rfcline reader fix.
---
parse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/parse.c b/parse.c
index 7ed1668f..95dea4bf 100644
--- a/parse.c
+++ b/parse.c
@@ -72,7 +72,7 @@ char *mutt_read_
> Would you mind creating a script to use for $editor. Something like:
>
> - - - - myeditor.sh - - - -
> #!/bin/bash
>
> cp $1 ~/before.txt
> vim $1
> cp $1 ~/after.txt
> - - - - end myeditor.sh - - -
>
> set editor = "~/myeditor.sh"
>
&g
> > I try to send this e-mail out in 7bit mode (with Ï
at the end of
> > Subject).
>
> Why would you do that when the discussion seems to be about UTF-8
> glyphs ? I'm curious.
I just thought that quoted printable did some work on the Subject
line, but I was wrong.
--
Kenichi Asai
On Wed, Aug 03, 2022 at 09:53:42AM +0900, Kenichi Asai wrote:
* In the step:
"- enter some e-mail address and a subject."
if instead, you put a å at the end of the subject here, before running vim,
does å show up in vim?
Yes.
If you then don't modify the subject whi
> > This e-mail has Ï
at the end of Subject. I will send it out.
>
> Somehow, the previous e-mail did not contain the replacement character
> at the end of Subject. I don't know why. Because the e-mail was
> quoted perhaps?
>
> [text/plain, quoted, utf-8, 1.3K]
> This e-mail has Ï
at the end of Subject. I will send it out.
Somehow, the previous e-mail did not contain the replacement character
at the end of Subject. I don't know why. Because the e-mail was
quoted perhaps?
[text/plain, quoted, utf-8, 1.3K]
Bastian's e-mail is 7bit (as i
Thank you all for considering this issue.
> * After you finish the above steps, what happens if you edit the email again
> in vim? Does the å show up at the end of the subject in vim the second time?
No. In vim, the character becomes ?? (two question marks).
> * With your origi
On 8/2/22 13:58:37, Kevin J. McCarthy wrote:
On Tue, Aug 02, 2022 at 03:52:51PM +0900, Kenichi Asai wrote:
When the subject ends with a character whose last byte in
UTF-8 is either 85 or A0, it appears the character collapses. >
I'm having trouble duplicating this problem on Debian T
On Tue, Aug 02, 2022 at 03:52:51PM +0900, Kenichi Asai wrote:
When the subject ends with a character whose last byte in
UTF-8 is either 85 or A0, it appears the character collapses.
To reproduce:
- prepare .mutt/muttrc containing only the following line:
set edit_headers=yes
- launch mutt and
On Tue, Aug 02, 2022 at 11:17:14PM +0700, Äoà n Trần Công Danh wrote:
> On 2022-08-02 13:07:42+0200, Dennis Preiser wrote:
>> On Tue, Aug 02, 2022 at 12:39:06PM +0200, Bastian wrote:
>> > Maybe some local vim/encoding issues on darwin?
>>
>> Maybe. Interestingl
On 2022-08-02 13:07:42+0200, Dennis Preiser wrote:
> On Tue, Aug 02, 2022 at 12:39:06PM +0200, Bastian wrote:
> > I see it in the subject now.
> > There are two U+FFFD chars.
> >
> >> | System: Darwin 21.6.0 (arm64)
> >> | ncurses: ncurses 6.3.20220625 (c
On Tue, Aug 02, 2022 at 12:39:06PM +0200, Bastian wrote:
> I see it in the subject now.
> There are two U+FFFD chars.
>
>> | System: Darwin 21.6.0 (arm64)
>> | ncurses: ncurses 6.3.20220625 (compiled with 6.3)
>> | libiconv: 1.16
>> | hcache backend: lmd
> > I can't reproduce either.
>
> I can reproduce the issue. In vim the character 0x52a0 is still present:
>
> <http://d--p.de/tmp/2022-08-02_vim.png>
>
> After quitting vim, mutt displays the unicode replacement character
> 0xfffd instead of 0x52a0:
I se
On Tue, Aug 02, 2022 at 04:04:07PM +0700, Äoà n Trần Công Danh wrote:
> On 2022-08-02 10:06:08+0200, Bastian wrote:
>> On 02Aug22 15:52+0900, Kenichi Asai wrote:
>> > Would it be possible to somehow avoid this problem? I cannot avoid
>> > creating e-mails with Jap
On 02Aug22 16:04+0700, Äoà n Trần Công Danh wrote:
> On 2022-08-02 10:06:08+0200, Bastian wrote:
> > Ï
0x3C5
> > ï¼
0xFF05
> > ï½
0xFF45
> > ã 0x30E0
> > å 0x52A0
> >
> > So only the last matches your description 'last byte is A0'
>
> I think he meant the last byte of their utf-8 repr
On 2022-08-02 10:06:08+0200, Bastian wrote:
> On 02Aug22 15:52+0900, Kenichi Asai wrote:
> > - prepare .mutt/muttrc containing only the following line:
> > set edit_headers=yes
> > - launch mutt and type m to create a new mail.
> > - enter some e-mail address and a
On 02Aug22 15:52+0900, Kenichi Asai wrote:
> - prepare .mutt/muttrc containing only the following line:
> set edit_headers=yes
> - launch mutt and type m to create a new mail.
> - enter some e-mail address and a subject.
> - vim launches.
> - edit Subject line so that it end
When the subject ends with a character whose last byte in
UTF-8 is either 85 or A0, it appears the character collapses.
To reproduce:
- prepare .mutt/muttrc containing only the following line:
set edit_headers=yes
- launch mutt and type m to create a new mail.
- enter some e-mail address and a
On Fri, Dec 24, 2021 at 05:18:57AM +, Sam Lee via Mutt-users wrote:
> Is it possible to make Mutt warn about an empty "Subject:" right before
> sending the email?
>
> The `abort_nosubject` configuration variable is not relevant here
> because `abort_nosubject` is
When I want to compose a new email, Mutt will prompt for the recipients
("To:"), followed by the subject ("Subject:"). How do I disable the
prompting for the subject? The `autoedit` configuration option will not
help here because it disables both prompts (i.e. both "To:
Is it possible to make Mutt warn about an empty "Subject:" right before
sending the email?
The `abort_nosubject` configuration variable is not relevant here
because `abort_nosubject` is only for configuring what happens when
there is no subject given at the subject prompt.
I am l
es by having both lines:
send-hook ~A 'unmy_hdr X-Priority'
send-hook '~s URGENT' 'my_hdr X-Priority: 1'
but apparently (acc. to the man page) send-hook only matches the recipients.
A send-hook can't be use to modify the recipients or subject of the
current
Hi mutt-lovers,
I just found that there seems to be no such thing as a subject-hook.
I was expecting that this would work:
send-hook '~s "URGENT"''my_hdr X-Priority: 1'
but apparently (acc. to the man page) send-hook only matches the recipients.
D
On 09.06.21 12:15, steve wrote:
> Hello,
>
> Nobody for this one?
>
> I found that I could modify the subject with a folder-hook but
that's
> only half of the solution since it doesn't take care of the group
alias
> part.
>
> Any help would be highly appr
Hello,
Nobody for this one?
I found that I could modify the subject with a folder-hook but that's
only half of the solution since it doesn't take care of the group alias
part.
Any help would be highly appreciated.
Steve
Le 02-06-2021, à 08:54:50 +0200, steve a écrit :
Hi,
In
Hi,
In the alias file, I defined several users and with them defined a group
'groupX'. When creating a new message with 'm' and calling 'groupX', I
would like to add a fixed text to the subject line (only when the alias
'groupX' is called').
On Sat, Oct 24, 2020 at 12:49:12PM -0700, Kevin J. McCarthy wrote:
> On Sat, Oct 24, 2020 at 12:24:23PM -0700, Kevin J. McCarthy wrote:
>> On Sat, Oct 24, 2020 at 02:04:11PM -0400, Remco Rijnders wrote:
>>> Unfortunately, the subject of such messages seems to get cleared. I
>&
Il 05 febbraio 2021 alle 12:25 Will Yardley ha scritto:
> On Fri, Feb 05, 2021 at 11:12:32AM -0800, Aleksandr Miroslav wrote:
> > What filter can I use to only show messages that contain emojis in the
> > subject line?
> >
> > For me, these are almost always spam,
On Fri, Feb 05, 2021 at 11:12:32AM -0800, Aleksandr Miroslav wrote:
> What filter can I use to only show messages that contain emojis in the
> subject line?
>
> For me, these are almost always spam, so I would like to quickly
> filter them out.
Seems like that might be challenging
What filter can I use to only show messages that contain emojis in the
subject line?
For me, these are almost always spam, so I would like to quickly
filter them out.
thanks
Alex
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Thanks, this works
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
> On Saturday,
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Hi,
An irritating
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
On Saturday, Octob
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Hi,
Looking at: h
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
On Friday, October
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
On Friday, Octobe
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Hi,
I want to set
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Hi,
New to mutt b
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Hi,
New to mutt bu
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
My aoologies for t
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Hi,
Sorry I am ver
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
Hi,
Sorry I am ver
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
AOL and Yahoo have
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
On 2020-09-01, at
This message wraps the original message.
The sending domain has a DMARC p=reject policy, which unfortunately
can cause bounces. See http://www.mutt.org/mail-lists.html#dmarc
To remove this message, please change the domain policy to p=none or
p=quarantine.--- Begin Message ---
(Plus one Bcc:)
O
On Sunday 19 August 2018 18:38,
Mihai Lazarescu put forth the proposition:
> On Sunday, August 19, 2018 at 14:57:20 +0100, David Woodfall wrote:
>
> > On Sunday 19 August 2018 13:58, Mihai Lazarescu put
> > forth the proposition:
> >
> > > BTW, piping the message through "formail -c" would
> > >
On Sunday, August 19, 2018 at 14:57:20 +0100, David Woodfall wrote:
On Sunday 19 August 2018 13:58, Mihai Lazarescu put forth
the proposition:
> BTW, piping the message through "formail -c" would
> concatenate continued fields in the header.
Can I add a pipe to the editor command somehow, or
On Sunday 19 August 2018 13:58,
Mihai Lazarescu put forth the proposition:
> On Sunday, August 19, 2018 at 10:33:35 +0100, David Woodfall wrote:
>
> > It was kind of an xy problem really. My vim function that
> > gets called when I edit a message needs fixing for subjects
> > of 1 line. Or it wi
On Sunday, August 19, 2018 at 10:33:35 +0100, David Woodfall wrote:
It was kind of an xy problem really. My vim function that
gets called when I edit a message needs fixing for subjects
of 1 line. Or it will drop me in insert mode after the first
line, and the second and any subsequent lines a
On Sunday 19 August 2018 16:52,
Erik Christiansen put forth the proposition:
> On 19.08.18 03:17, David Woodfall wrote:
> > I sent a message with a rather long subject line earlier and it was
> > split into two lines.
>
> OK, I'm a laggard, still on mutt 1.8.0, but w
On 19.08.18 03:17, David Woodfall wrote:
> I sent a message with a rather long subject line earlier and it was
> split into two lines.
OK, I'm a laggard, still on mutt 1.8.0, but when I compose a three-line
subject in vim¹, separated by newlines, it is visually _joined_ into a
sin
On Sunday 19 August 2018 08:25,
Mihai Lazarescu put forth the proposition:
> On Sunday, August 19, 2018 at 03:17:58 +0100, David Woodfall wrote:
>
> > Or is this a limitation of the RFC that subject lines need
> > to be under a certain length?
>
> Yes, RFC 5322. Header
On Sunday, August 19, 2018 at 03:17:58 +0100, David Woodfall wrote:
Or is this a limitation of the RFC that subject lines need
to be under a certain length?
Yes, RFC 5322. Header lines cannot exceed 998 characters and
should be folded at less than 78 character per line:
https
I sent a message with a rather long subject line earlier and it was
split into two lines.
Is there a way to avoid that? I tried setting tw=0 in an autocmd in
vim but it still got cut. I checked that tw was still set to 0, so I
assume that mutt cuts it before vim opens it.
Or is this a limitation
On 28.02.18 12:10, Patrick Shanahan wrote:
> some time ago, in an earlier age, Sven Guckes posted a sed or perl filter
> to hide "Subject:" additions, but I seem to have lost it, and he seems to
> be missing too :^(
>
The following has served for so many years in my .p
Kevin J. McCarthy writes:
> On Wed, Feb 28, 2018 at 09:28:41AM -0700, Akkana Peck wrote:
> > But the example in the manual doesn't work for me in 1.9.3 [ ... ]
> > subjectrx '\[[^\]]*\]? *' '%L%R'
>
> Looks like the example might be wrong in the manual, unless there are
> regexp library differen
On Wed, Feb 28, 2018 at 07:05:19PM +0100, Matthias Apitz wrote:
> El día Wednesday, February 28, 2018 a las 10:00:29AM -0800, Kevin J. McCarthy
> escribió:
>
> > Looks like the example might be wrong in the manual, unless there are
> > regexp library differences. Because ']' is first in the char
El día Wednesday, February 28, 2018 a las 10:00:29AM -0800, Kevin J. McCarthy
escribió:
> Looks like the example might be wrong in the manual, unless there are
> regexp library differences. Because ']' is first in the character
> class (after the negation), it shouldn't need to be escaped. This
On Wed, Feb 28, 2018 at 09:28:41AM -0700, Akkana Peck wrote:
> Todd Zullinger writes:
> > http://www.mutt.org/doc/manual/#display-munging
> >
> > subjectrx was added in 1.8.0, it seems.
>
> That's wonderful! Something I've been wishing for for a long time.
>
> But the example in the manual doesn
On 2018-02-28 12:10, Patrick Shanahan wrote:
> some time ago, in an earlier age, Sven Guckes posted a sed or perl
> filter to hide "Subject:" additions, but I seem to have lost it, and
> he seems to be missing too :^(
Here's what I do now as part of my incoming pipeline.
* Patrick Shanahan on Wednesday, February 28, 2018 at 12:10:59 -0500
some time ago, in an earlier age, Sven Guckes posted a sed or perl filter
to hide "Subject:" additions, but I seem to have lost it, and he seems to
be missing too :^(
Something like
sed -e '1,/^$/ s/
{1,} don't match anything and do don't
> do any substitution.
>
> The feature is still great, because I don't strictly need the regex
> -- I can make explicit matches for the few really long list names
> that are causing problems -- but I wonder why the example in the
* Akkana Peck on Wednesday, February 28, 2018 at 09:28:41 -0700
Todd Zullinger writes:
http://www.mutt.org/doc/manual/#display-munging
subjectrx was added in 1.8.0, it seems.
That's wonderful! Something I've been wishing for for a long time.
But the example in the manual doesn't work for me
need the regex
-- I can make explicit matches for the few really long list names
that are causing problems -- but I wonder why the example in the
manual isn't working.
Also, is it possible to escape a quote? I have one set of emails
that come through with an apostrophe, like
Subject: [Don't c
On Tue, Feb 27, 2018 at 10:43:05AM -0500, Todd Zullinger wrote:
> http://www.mutt.org/doc/manual/#display-munging
> subjectrx was added in 1.8.0, it seems.
Thanks so much, I've been feeling the need for this for
a long time, finally satisfied :)
--strk;
On 27Feb2018 10:39, Ralf Hildebrandt wrote:
I'm using:
# Erase [ext] tags from e-mails
subjectrx '\[ext\] *' '%L%R'
to remove the tag "optically". Is there any way of removing the
Subject: prefix when answering/forwarding?
Can't speak for forward
Matthias Apitz wrote:
> El día Tuesday, February 27, 2018 a las 10:39:53AM +0100, Ralf Hildebrandt
> escribió:
>> I'm using:
>>
>> # Erase [ext] tags from e-mails
>> subjectrx '\[ext\] *' '%L%R'
>>
>> to remove the tag &q
El día Tuesday, February 27, 2018 a las 10:39:53AM +0100, Ralf Hildebrandt
escribió:
> I'm using:
>
> # Erase [ext] tags from e-mails
> subjectrx '\[ext\] *' '%L%R'
>
> to remove the tag "optically". Is there any way of removing the
>
I'm using:
# Erase [ext] tags from e-mails
subjectrx '\[ext\] *' '%L%R'
to remove the tag "optically". Is there any way of removing the
Subject: prefix when answering/forwarding?
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité -
Hi,
check out edit_headers and autoedit in the handbook. I'm assuming you
have a relatively new version of Mutt.
On Monday, 20 November at 12:19, Pétùr wrote:
> Hi,
>
> Is there a way to quickly clear the subject of an email?
>
> Right now I have to delete character by ch
Pétùr:
> Is there a way to quickly clear the subject of an email?
> Right now I have to delete character by character with the del key.
> I want to delete everything in the subject field and add a better
> (new) subject sometimes when forwarding email.
I almost always jump into vim
On Mon, Nov 20, 2017 at 08:42:28AM -0500, Ben Boeckel wrote:
On Mon, Nov 20, 2017 at 12:19:10 +0100, Pétùr wrote:
Is there a way to quickly clear the subject of an email?
Right now I have to delete character by character with the del key.
I want to delete everything in the subject field and
On Mon, Nov 20, 2017 at 02:18:52PM +0100, Pétùr wrote:
> I noticed also that C-k was working (but the cursor has to be at the
> beginning of the line).
Which can be achieved by C-a, in case you're interested.
Cheers,
Tom
--
A beginning is the time for taking the most delicate care that balance
* Pétùr [11-20-17 07:21]:
> Hi,
>
> Is there a way to quickly clear the subject of an email?
>
> Right now I have to delete character by character with the del key.
>
> I want to delete everything in the subject field and add a better
> (new) subject sometimes when f
Pétùr wrote (Mon 2017-Nov-20 12:19:10 +0100):
> Is there a way to quickly clear the subject of an email?
Pressing Ctrl+U while editing the field should do what you are
looking for.
Cheers, Marcus
--
Marcus C. Gottwald ·· https://cheers.de
On Mon, Nov 20, 2017 at 01:24:01PM +0100, Francesco Ariis wrote:
On Mon, Nov 20, 2017 at 12:19:10PM +0100, Pétùr wrote:
Hi,
Is there a way to quickly clear the subject of an email?
Right now I have to delete character by character with the del key.
I want to delete everything in the subject
Control-U ?
--hymie! http://lactose.homelinux.net/~hymiehy...@lactose.homelinux.net
On Mon, Nov 20, 2017 at 12:19:10PM +0100, Pétùr wrote:
> Hi,
>
> Is there a way to quickly clear the subject of an email?
>
> Right now I have to delete character by character with the
Hi,
Is there a way to quickly clear the subject of an email?
Right now I have to delete character by character with the del key.
I want to delete everything in the subject field and add a better
(new) subject sometimes when forwarding email.
Pétùr
unsubscribe
--
Puketoi
Te Matuku Point
Waiheke Island
On 2015年12月29日 17時37分, Florian Lohoff wrote:
Our companys "virus" check adds really annoying "*** unchecked ***" to
every encrypted mails subject.
Is there a way to suppress certain parts of a subject before displaying
in the folder view?
By "folder" vi
On Tue, Dec 29, 2015 at 11:23:31AM -0800, Ian Zimmerman wrote:
> On 2015-12-29 17:37 +0100, Florian Lohoff wrote:
>
> > Our companys "virus" check adds really annoying "*** unchecked ***" to
> > every encrypted mails subject.
> >
> > Is there a
On 2015-12-29 17:37 +0100, Florian Lohoff wrote:
> Our companys "virus" check adds really annoying "*** unchecked ***" to
> every encrypted mails subject.
>
> Is there a way to suppress certain parts of a subject before displaying
> in the folder view?
>
Hi,
Our companys "virus" check adds really annoying "*** unchecked ***" to
every encrypted mails subject.
Is there a way to suppress certain parts of a subject before displaying
in the folder view?
To my mind comes also mailinglist tags to suppress.
Fl
On Sun, Oct 18, 2015 at 02:59:38PM +0200, Francesco Ariis wrote:
> On Sun, Oct 18, 2015 at 02:49:27PM +0200, Teon Banek wrote:
> > Hello everyone,
> >
> > Is it possible to have a default subject prefix when sending a mail to a
> > group? For example, I have a grou
On Sun, Oct 18, 2015 at 02:49:27PM +0200, Teon Banek wrote:
> Hello everyone,
>
> Is it possible to have a default subject prefix when sending a mail to a
> group? For example, I have a group of people and I'd like to
> automatically fill in the subject with '[Group]&#x
Hello everyone,
Is it possible to have a default subject prefix when sending a mail to a
group? For example, I have a group of people and I'd like to
automatically fill in the subject with '[Group]' when sending mail to
all members of the group. Basically, what I want is
* Артур Истомин [06-15-15 15:34]:
> On Mon, Jun 15, 2015 at 07:45:02PM +0300, Staffan Thomén wrote:
> > unsubscribe
>
> Come on, Staffan! Where are you going?!
Well, if he can't figure it out, probably has no business with mutt :)
doah
--
(paka)Patrick Shanahan Plainfield, Indiana, USA
On Mon, Jun 15, 2015 at 07:45:02PM +0300, Staffan Thomén wrote:
> unsubscribe
Come on, Staffan! Where are you going?!
>
El día Monday, June 15, 2015 a las 07:45:02PM +0300, Staffan Thomén escribió:
> unsubscribe
No! I will not unsubscribe me.
--
Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211
+49-176-38902045
"Wenn der Mensch von den Umständen gebildet wird, so muß man die Umstände
unsubscribe
* Chris Down on Tuesday, July 15, 2014 at 11:45:26 +0800
> Is there some way to disable the prompts for To/Cc/Subject when replying
> to a message, but still have them appear when creating a new one?
Try:
set fast_reply=yes
--
theatre - books - texts - movies
Black Trash Productions a
* On 14 Jul 2014, Chris Down wrote:
> Hello,
>
> Is there some way to disable the prompts for To/Cc/Subject when replying
> to a message, but still have them appear when creating a new one?
>
> Thanks. :-)
Not directly, but you can probably construct a macro that plugs in ENT
Hello,
Is there some way to disable the prompts for To/Cc/Subject when replying
to a message, but still have them appear when creating a new one?
Thanks. :-)
* Martin Vegter [2014-06-19 14:56 +0200]:
> Hello,
> when I pres "s" to save an attachment (i.e. foo.pdf), Mutt asks me:
>
> Save to file: foo.pdf
>
> Is there a way to prepend "~/tmp/" in front of the name, so that by
> default all files are saved in "~/tmp/"? Basically, I would like mutt
approve 48zvVL unsubscribe mutt-users shawnzaiderm...@gmail.com
approve 48zvVL unsubscribe mutt-dev shawnzaiderm...@gmail.com
1 - 100 of 505 matches
Mail list logo
