On Monday, November 21, 2005 at 10:44:12 +0800, WANG Xu wrote:
The failed mail is attached as mailfail.gz
It is a well-formed Latin-1 mail, with 1 e acute in From:, and 2
in signature. As the e acute exists in GBK charset (printf \xa8\xa6),
the mail should be perfectly displayed.
with
On Tuesday, November 29, 2005 at 8:59:01 +0800, WANG Xu wrote:
the segfault occured even in:
| LANG=en_US
| LC_CTYPE=zh_CN.GBK
The charset of all the categories must be the same as the terminal,
or strictly compatible. In your case only GBK or US-Ascii. That en_US
having an implicit
On Thursday, December 1, 2005 at 11:34:17 +0800, WANG Xu wrote:
On Tue, Nov 29, 2005 at 01:40:44PM +0100, Alain Bench wrote:
remove LC_CTYPE, and set back LANG=zh_CN.GBK.
do you mean this:
| $ locale
| LANG=zh_CN.GBK
| LC_CTYPE=
| LC_ALL=
Almost: Yet unset LC_CTYPE, or rather remove
: On your GBK terminal, is it a half-wide character as Ascii e,
or full-width as Chinese chars?
On Fri, Dec 02, 2005 at 08:40:19PM +0100, Alain Bench wrote:
Character U+00BF not existing in GBK, therefore masked by a question
mark for you on display, and quoted in your reply. In these
conditions
Hello Daniel, thanks for the report and the digging.
On Friday, October 7, 2005 at 9:45:08 -0700, Daniel Burrows wrote:
I fixed it by going through and replacing each space character in
index_format with a space character.
Nice one! Your original $index_format has all spaces as Latin-1
Synopsis: can't view-attachments of a message/rfc822 attachment
view-attached in compose
Comment added by ab on Tue, 01 Nov 2005 09:55:05 +0100
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Synopsis: can't view-attachments of a message/rfc822 attachment
view-attached in compose
Comment added by ab on Tue, 01 Nov 2005 10:00:38 +0100
crossref /2085 closed duplicate
add /2085 reporter to notifieds
retitle from inaccurate Subject:view-header (v) does not work in forwarded
Hello Brian, and much thanks for the problem report!
On Monday, October 31, 2005 at 20:23:01 -0500, Brian Clark wrote:
After upgrading to Mutt 1.5.11-2, when starting mutt, I get the error:
| Error in /home/brian/.mutt/rc.private, line 62: [: invalid command
Line 62 of
Hello Lars,
On Wednesday, October 12, 2005 at 12:54:46 +0200, Lars Persson Fink wrote:
to save a thread to a mailbox when in the pager.
| macro pager F42 \
| exit\
| enter-commandunset resolveEnter\
| tag-thread\
| enter-commandset resolveEnter\
| tag-prefix\
| save-message=aEntery\
|
Synopsis: Screen left in strange mode when piping mail with unknown mime-types
Comment added by ab on Thu, 13 Oct 2005 20:22:05 +0200
Deduppe and devirus unformatted trail.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Hello, and thank you very much for the report.
On Thursday, November 17, 2005 at 11:24:20 +0800, WANG Xu wrote:
I am using mutt to read mailing list, and segfault occured sometimes.
And I found it will occur whenever the mail's ``From'' is in ISO8859-1
encoding, and if I remove the
Hi Ambrose, and thanks for the interesting suggestion.
On Thursday, December 7, 2006 at 11:03:01 -0500, Ambrose Li wrote:
In practice, GB-based Chinese emails with traditional characters are
tagged as GB2312 even though technically speaking they are in
GB18030.
So you can correct this
Hello Michelle,
On Friday, November 10, 2006 at 18:23:02 +0100, Michelle Konzack wrote:
In the Index-View I have: électro
and then in the message: électro
Perhaps the header cache was filed while $charset=utf-8, and not
wiped when you changed to the Latin-9 locale? Or some setting
Hello Georg, and many thanks to you for the report.
On Friday, October 13, 2006 at 23:53:27 +0200, Georg Neis wrote:
% mutt -f crash
Sorting mailbox...zsh: segmentation fault (core dumped) mutt -f crash
Unreproducible here. Could you please check the backtrace? Let
segfault create a
On Friday, December 8, 2006 at 21:12:59 -0500, Ambrose Li wrote:
On Fri, Dec 08, 2006 at 06:36:26PM +0100, Alain Bench wrote:
| charset-hook ^gb2312$ gb18030
How many such under-labelled mails do you receive?
I only receive such mails from time to time.
Small benefit, but zero drawback
Hello Allan,
On Monday, September 25, 2006 at 10:55:44 -0400, Allan Wind wrote:
mutt remembers the Content-Disposition but does not allow me to easily
change it.
What about the function:
| Compose:
| ^Dtoggle-disposition toggle disposition between inline/attachment
Bye!
package mutt
close 347375
thanks
Hello Dmitry, and thanks for reporting this problem.
On Tuesday, January 10, 2006 at 14:07:10 +0200, Dmitry Nezhevenko wrote:
mutt show N for _all_ mailboxes including mailboxes without new mail.
You are most probably using mbox folders on a noatime
package mutt
close 347256
thanks
Hello, thanks for this report.
On Monday, January 9, 2006 at 19:57:20 +0100, A.M.P. Boelens wrote:
When I type M to see all my mailboxes, mutt not always indicates
that there is a new e-mail in a specific mailbox (by putting an N in
front of it) while, when
Hello Loïc, and thanks for the good report.
On Tuesday, December 11, 2007 at 17:30:13 +0100, Loïc Minier wrote:
My terminal is completely garbled when I load up a particular message
The only unusual thing in this message is that 4 lines begin by a
character U+FEFF (the ZERO WIDTH NO-BREAK
[ Courtesy Copy to Ilya Konstantinov, ]
[ Mutt bug #1269, and Debian Bug #152444 ]
On Saturday, February 19, 2005 at 12:41:10 PM +0900, Tamotsu Takahashi wrote:
The problem is that MS thinks ISO-2022-JP means ISO-2022-JP-MS. And MS
does not think there is a charset called
Hello Benoît-Pierre, and thanks for the report,
On Monday, March 7, 2005 at 1:43:40 AM +0100, Benoît-Pierre Demaine wrote:
| LANG=en_GB.ISO-8859-15
| LC_ALL=
[Mutt] keeps asking me questions in french
Hum... So there seems to be a locale/NLS mismatch. But why? Could
you please verify:
·
package mutt
close 298673
thanks
Hello Matthew, and thanks for the report,
On Wednesday, March 9, 2005 at 12:45:59 AM -0700, Matthew Mueller wrote:
emails with:
| Content-Type: text/plain; charset=utf-8
| Content-Transfer-Encoding: base64
using limits doesn't work on them. Ex: l~bdpkg shows
Hi Marco!
On Friday, March 11, 2005 at 2:28:40 PM +0100, Marco d'Itri wrote:
On Mar 11, Sergey Kogan [EMAIL PROTECTED] wrote:
Many mailers [...] use rfc2047-encoded suggested filenames
This is a standard violation which is not tolerated by the upstream
author (and me as well) and such a
package mutt
submitter 298365 Benoît-Pierre Demaine [EMAIL PROTECTED]
close 298365
thanks
Salut Benoît-Pierre,
To discuss the bug report, you must mail to [EMAIL PROTECTED]
Otherwise informations are lost for everyone else, as I will not forward
private mails. And please use valid sender
package mutt
tags 152444 patch
thanks
On Monday, February 21, 2005 at 10:32:24 AM +0900, Tamotsu Takahashi wrote:
On Sun, Feb 20, 2005 at 03:45:21PM +0100, Alain Bench wrote:
Impossible to set iso-8859-8-i in $send_charset, and to influence
that with an iconv-hook. Wouldn't your patch-1.5.8
package mutt
tags 269699 patch fixed-upstream
thanks
Hello Kyle,
On Thursday, February 24, 2005 at 2:00:04 AM -0500, Kyle Wheeler wrote:
If it helps, here's the [ddm.pgp-auto-decode] patch.
Thanks, but the previous URL was sufficient. Anyway the
ddm.pgp-auto-decode patch is now included
Hello Adrian, and thank you for this suggestion.
On Wednesday, September 12, 2007 at 7:46:26 +0200, Adrian Bunk wrote:
In the third millenium, with virtually all software supporting UTF-8
and most users using UTF-8 locales, it would be nice if this [default
$send_charset] could be changed to
, this is an excellent argument for inserting
Latin-9 into the default $send_charset, between Latin-1 and UTF-8. I'm
not against such change: Once granted Mutt already has a moderately
western-centric default config, why not make it better?
On Thu, Sep 20, 2007 at 04:57:11PM +0200, Alain Bench
Hello Owen, and much thanks for the problem report.
On Thursday, September 27, 2007 at 12:06:05 -0500, Owen Heisler wrote:
Every time a pgp signed message is viewed in mutt's pager, I have to
redraw the screen (^L) in order to read the message, as the gpg output
scrolls up the text on the
package mutt
# misconfiguration issue
close 444318
thanks
On Saturday, October 13, 2007 at 11:17:45 -0500, Owen Heisler wrote:
Thanks and sorry for the noise!
No problem: Better a false alarm than a missed bug. ;-)
Bye!Alain.
--
Give your computer's unused idle processor cycles to
Hello Dan, and thank you very much for your reports.
On Sunday, August 12, 2007 at 19:42:05 +0800, Dan Jacobson wrote:
Upon encountering postpone this message?, the user worries if n
will 1. throw away the message, or 2. go ahead and send the message,
or 3. let him continue to edit the
Bonjour Loïc,
Le samedi 4 août 2007 à 17:58:05 +0200, Loïc Minier écrivait:
I often want to set/clear some flags on a message I'm reading; for
example mark it as important.
Try flag-message function to toggle a message's 'important'
flag, by default bound to the [F] key.
I wish the
Le mardi 28 août 2007 à 22:50:12 +0200, Loïc Minier écrivait:
unfortunately, [pager's flag-message] only works for the
important flag
The pager has functions for manipulating many flags:
| flag key functionhelp
package mutt
close 413144
thanks
Hello Claus, and thank you for your report.
On Friday, March 2, 2007 at 19:52:28 +0100, Claus Fischer wrote:
When saving a messages with decode-save, mutt strips most headers.
decode-save obeys $weed. This is the intended behaviour from the
beginning,
On Saturday, March 3, 2007 at 15:50:11 +0100, Claus Fischer wrote:
they want a decrypt and save, but not a decrypt then lose headers then
save :-)
Don't mix code and crypt. The function decrypt-save does a
nearly verbatim move, where only PGP and S/MIME encrypted parts get
decrypted.
Synopsis: send_charset doesn't support charset-hook'd charsets
Comment added by ab on Tue, 06 Mar 2007 20:13:12 +0100
upload patch-1.5.12.msyk.iconvhook.1-ab patch with comments
deduppe unformatted.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Hi Ambrose, and as usual much thanks for reporting bugs!
On Thursday, December 7, 2006 at 12:01:58 -0500, Ambrose Li wrote:
In an allegedly-GB2312 string, any high byte following pure ASCII
should be treated as the lead byte of a presumed double-byte
character, even if it is invalid GB2312.
Hi Christoph,
On Friday, March 9, 2007 at 17:50:24 +0100, Christoph Berg wrote:
does fixing this also affect #249626/402035?
The hooks fixing #402027 will also prevent most the symptoms
described in #402035 (only the unconvertable ?h stays). But the
underlying problem is still there, and
package mutt
close 414828
thanks
Hello Joerg, and thanks for the report.
Am Mittwoch 14 März 2007 um 0:28:03 +0100, Joerg Friedrich schrieb:
my locale is LANG=de_DE.UTF-8 when I reply to utf-8 encoded mails, the
attribution is encoded in iso8859-1 because strftime does not know
about
package mutt
# time for a debate
reopen 414828
retitle 414828 mutt: wish localized default $locale
severity 414828 wishlist
thanks
Hello Christoph,
On Sunday, March 25, 2007 at 23:12:59 +0200, Christoph Berg wrote:
I wonder if $locale shouldn't default to $LC_TIME
I fully agree, that
Hello Nik, and thanks for the report.
On Wednesday, February 14, 2007 at 12:10:41 -0500, Nik A. Melchior wrote:
When I view an email with an attachment, e.g. a PDF document, the
status line complains:
mailcap entry for type application/pdf not found
However, /etc/mailcap does indeed include
package mutt
close 389405
thanks
Hello Allan,
On Tuesday, October 10, 2006 at 10:20:03 -0400, Allan Wind wrote:
| Compose:
| ^D toggle-disposition toggle disposition between inline/attachment
[I] did check the manual and found no mention of it.
Since 1.5.14+cvs20070315-1 package,
On Monday, March 26, 2007 at 17:26:53 +0200, Christoph Berg wrote:
which parts are all affected.
$locale impacts $date_format, and all $*_formats having date
%expandos.
Environment impacts the browser at startup (later browser becomes
English, flea/1734), and some dates here and there
Hello Kyle!
On Monday, March 26, 2007 at 9:47:04 -0600, Kyle Wheeler wrote:
Should [$locale] then perhaps be renamed to $date_locale, just for
more clarity?
Sure yes, good idea! Only if Rado agrees, of course. With a
compatibility synonym. $locale is a very imprecise and confusing name.
Hi Kyle!
On Monday, March 5, 2007 at 15:43:22 -0700, Kyle Wheeler wrote:
On Sunday, March 4 at 01:00 AM, quoth Alain Bench:
no way to automatically reset $weed to its previous state.
Sure you can:
Unfortunately too nice to be true. There is a vicious trap: The
prompt for a filename
Hello Christoph,
On Tuesday, February 27, 2007 at 23:20:25 +0100, Christoph Berg wrote:
did you try the charset-hook suggested here? Does it work for you?
I'm not Ambrose, but have no doubt it worked. ;-)
If so I'd be inclined to include it in /etc/Muttrc.
Then I'll contribute
Hello John, and thank you for this report.
On Sunday, May 6, 2007 at 17:50:29 -0400, John Morrissey wrote:
When displaying an index in threaded mode, the thread markers (for
messages nested in a thread) make lines wrap correctly. After some
movement of the highlight bar, the display becomes
Bonjour Marc,
On Thursday, May 10, 2007 at 19:55:34 +0200, Marc Glisse wrote:
even with the -g option, ntp refuses to step 4 years
This is not normal. However it can happen in some situations, like
with some reference clocks rejecting large offsets despite -g, or when a
LOCAL() clock
package mutt
close 420854
thanks
Hi John-Marc,
On Thursday, April 26, 2007 at 14:21:16 -0700, John-Marc Chandonia wrote:
It turned out to be a bug in textmail (http://raf.org/textmail/), so
I'll report it to the author. There doesn't seem to be a Debian
package for the program.
Thanks
Hello John-Marc, and thanks for this report.
On Tuesday, April 24, 2007 at 18:48:02 -0700, John-Marc Chandonia wrote:
When I send a test message to myself without any attachments, the
signature validates correctly. However, if I attach anything to the
message, my signature does not validate;
Hello Vaclav, and thank you for this interesting suggestion,
On Thursday, April 19, 2007 at 15:26:44 +0200, Vaclav Ovsik wrote:
Openssl (OpenSSL 0.9.8c 05 Sep 2006) suppresses message body in case
of verifycation failure (e.g. not trusting CA) [...] nothing is
displayed, but openssl error.
On Tuesday, April 24, 2007 at 14:56:45 +0200, Axel Beckert wrote:
my .mutt/muttrc indeed has that line:
| set charset=iso-8859-1
I assume you meant $config_charset? Otherwise you should better not
set $charset, so it is free to automatically follow whatever is the
current locale.
to
On Friday, April 27, 2007 at 9:40:27 +0200, Václav Ovsík wrote:
I didn't found anything about this behaviour in smime man page and
I didn't test of this with older openssl 0.9.7 (perhaps not
interesting for Debian). I hope this behaviour (supressing output on
failure) will be consistent from
On Thursday, April 26, 2007 at 14:10:08 +0200, Alain Bench wrote:
To me this seems appropriate, both for Debian /etc/Muttrc and upstream
contrib/smime.rc
That's now fixed upstream. I don't set the fixed-upstream tag here,
because of the different place (/etc/Muttrc) where the fix has
Hello again Lionel,
On Saturday, May 26, 2007 at 18:19:40 +0200, Lionel Elie Mamane wrote:
change mutt to use sendmail -t
Danger: This is known to generate duplicate mails with some sorts of
sendmails.
a new configuration option write_bcc_fcc
Probably useless: There is no much
Hello Lionel, and much thanks for the analysis and solution.
On Saturday, May 26, 2007 at 20:39:04 +0200, Lionel Elie Mamane wrote:
The attached patch changes all calls to strtok to the reentrant
strtok_r, fixing that problem.
But strtok_r() doesn't exist on some platforms, so I fear
On Wednesday, May 30, 2007 at 13:58:41 +0200, Lionel Elie Mamane wrote:
There is already a patch that does just that: make $write_bcc not
impact $record.
Which patch? The Gmane link you gave unfortunately doesn't work for
me. The only patch I tested doing that was posted to the mutt-users
On Thursday, May 17, 2007 at 21:38:10 -0400, John Morrissey wrote:
I tried Mac OS X's Terminal again and the index lines are still
wrapping with LANG=en_US.UTF-8 and Terminal - Window Settings... -
Display - Character Set Encoding set to Unicode (UTF-8).
The ACS chars seem OK, but
On Saturday, May 19, 2007 at 12:26:13 -0400, John Morrissey wrote:
there is [in Terminal.app] a setting called 'Wide glyphs for
Japanese/Chinese/etc.' Unchecking this made these characters appear
properly
Fine! Otherwise Takashi Takizawa coded a patch-1.5.14.tt.wcwidth.3
for Mutt,
Hello Axel, and thank you for reporting us this problem.
On Monday, April 23, 2007 at 15:08:27 +0200, Axel Beckert wrote:
| set index_format=%4C %Z %[%a·%d·%b] %-16.16F [%-12.12L] (%4c %4l) %s% %M
It works fine since years and even inside uxterms with
LC_CTYPE=en_US.UTF-8, but no other locale
package: debbugs
severity: minor
Hello!
On the Debian PTS I subscribed to the bug mailing list of source
package package. I then received a confirmation challenge like that:
+---
| From: Debian Package Tracking System
Hello Rick, and thanks for reporting this.
On Thursday, July 14, 2005 at 8:48:45 AM -0400, Rick Pasotto wrote:
Version: 1.5.9-2
After pressing 'e' to edit a message in the mailbox, the original is
marked as deleted (as it always has been) but the edited version is
now nowhere to be found.
package mutt
close 316512
thanks
Hello Wolfgang, thank you for the precise report.
On Friday, July 1, 2005 at 3:30:26 PM +0200, Wolfgang Weisselberg wrote:
| send2-hook . 'my_hdr From: [EMAIL PROTECTED]'
observe: From IS NOT SET!
That is not a bug, things are designed like that. At the
Hi Adeodato!
On Saturday, August 20, 2005 at 2:59:34 PM +0200, Adeodato Simó wrote:
* Sven Luther [Sat, 20 Aug 2005 14:12:21 +0200]:
even if my encoding settings where fubar, mutt should be copying the
line verbatim
An invalid byte would have perturbated later operations.
it's not
Hello Tony, thanks for the report.
On Thursday, August 18, 2005 at 12:58:11 AM +0100, Tony Houghton wrote:
When replying by email, slrn ignores some options such as username and
hostname, defaulting to system settings. In my case this doesn't
produce a valid email address for the From:
On Monday, August 22, 2005 at 11:37:22 PM +0200, Wolfgang Weisselberg wrote:
the manual schould mention edit-from:
| However, you cannot set From: with send2-hook except using
| 'send2-hook . push edit-fromkill-line[EMAIL PROTECTED]Enter',
| since send2-hook runs too late for any other method.
package mutt
close 324770
thanks
Hello Martin, and thanks for the report.
On Wednesday, August 24, 2005 at 2:02:43 AM +0100, Martin Michlmayr wrote:
Actually, it seems this may be partly due to a broken message. I saw
that the Subject line is not encoded which (I think) is against RFC.
In
Hello Christoph, Enrico, and Grant: Thank you all for your bug reports.
On Thursday, June 24, 2004 at 4:05:01 PM +0200, Christoph von Stuckrad wrote:
I set a limit, which 'just now' results in 'nothing' Correctly I get
the message No messages matched criteria. [...] new mail comes in...
***
package mutt
close 318270
thanks
On Sunday, July 17, 2005 at 11:46:54 AM +0200, Alain Bench wrote:
No such bug with stock Mutt 1.5.9 here
Unreproducable, and silent reporter: Closing.
Bye!Alain.
--
DGC you have a talent for drawing people I'd usually be happy reading
DGC into your
package mutt
close 322040
thanks
Hello Bryan, and thanks for the report.
On Monday, August 8, 2005 at 3:12:35 PM -0700, Bryan Richter wrote:
I have two external mailboxes; one is imaps and the other is pop. What
I want to do is change my From: header to match the address that each
mailbox
Hello Chris, and thanks for the report.
On Sunday, July 10, 2005 at 12:25:16 PM -0700, Christian H. Stork wrote:
Version: 1.5.9-2
If I do a tag-reply (or tag-group-reply) of several messages in the
same thread then mutt only quotes the first message and forgets about
the rest.
No such
On Wednesday, July 13, 2005 at 11:51:33 AM -0700, Christian H. Stork wrote:
If tmpdir is set then the multi-quote is cut off at the beginning of
the sig in the first message. If it's not set everything (including
the sig) is quoted.
Truncated at around 84 bytes? This may smell like a
Hello Tobias, and thank you for the report.
On Wednesday, February 8, 2006 at 10:47:32 +0100, Tobias Stefan Richter wrote:
I just saved an attachment by the name
=?ISO-8859-15?Q?=DCberraschung=2Ezip?= as it was received due to
(improper?) encoding.
Illegal encoding, explicitly
package mutt
retitle 364941 mutt: wish less strict RFC 2047 header decoding
severity 364941 wishlist
tags 364941 patch
thanks
Hello Dmitry, and thank you for the report.
On Thursday, April 27, 2006 at 0:02:52 +0400, Dmitry E. Oboukhov wrote:
in .muttrc: set rfc2047_parameters = yes
The
On Friday, April 28, 2006 at 10:54:17 +0400, Dmitry E. Oboukhov wrote:
On 12:24 Thu 27 Apr , Alain Bench wrote:
The $rfc2047_parameters setting is relevant to attachment filename
decoding, not to subject.
And why is it not relevant for subject?
All hi-bit subjects are (or should
package mutt
close 360912
thanks
Hello Pascal, and thank you for reporting us this problem.
On Wednesday, April 5, 2006 at 16:01:30 +0200, Pascal A. Dupuis wrote:
[mailcap] deletion of the temp file occurs too early, before galeon
get a chance to load it.
Mutt deletes the temporary
package mutt
retitle 339555 regexec(): Latin chars segfault in Chinese locales
reassign 339555 libc6
thanks
Hello,
On Monday, December 5, 2005 at 22:33:34 +0800, WANG Xu wrote:
Thanks for your explanation and hope the informations helpful.
And thank you again for the precise report. Ye
Hello Thomas, and thank you for your reports.
On Friday, June 9, 2006 at 11:38:33 +0200, Thomas Bleher wrote:
When trying to attach
http://www.cip.ifi.lmu.de/~bleher/mutt-mime-bug.tar.gz , mutt assigns
the file the type and encoding text/plain, quoted, utf-8
The foolable heuristic Mutt
Hello Joshua, and thank you for the suggestion.
On Saturday, July 1, 2006 at 17:25:21 +0200, Joshua Dunamis wrote:
I home thet in the futur i possible to view the html format mail
directly form mutt, may be with integration with links2 or with a
frame buffer interface of mutt
Mutt is
package mutt
close 384351
thanks
Hello Julian, and thank you for reporting us this problem.
On Wednesday, August 23, 2006 at 18:21:21 +0100, Julian Gilbey wrote:
| application/msword; oowriter '%s'; edit=oowriter '%s';
BTW, there should not be single quotes around %s in mailcap.
when
Hello Rene,
On Sunday, August 27, 2006 at 18:38:42 +0200, Rene Engelhard wrote:
On Sun, Aug 27, 2006 at 02:06:04PM +0200, Alain Bench wrote:
| application/msword; oowriter '%s'; edit=oowriter '%s';
there should not be single quotes around %s in mailcap.
Why?
Because Mutt has to do
On Sunday, August 27, 2006 at 16:54:12 +0100, Julian Gilbey wrote:
Unfortunately, mutt_bgrun doesn't work either: oowriter exits
immediately and so the temporary file gets deleted before the new
oowriter process which is called has time to read it.
mutt_bgrun does the backgrounding; The
Hello Robert, and thank you for this interesting suggestion.
On Tuesday, September 5, 2006 at 20:37:36 +0200, Robert Millan wrote:
to work around buggy clients that send mail with a non-ascii charset
_but_ without any Content-Type.
| unset strict_mime
| set assumed_charset=iso-8859-1
Hello Thomas,
On Wednesday, August 16, 2006 at 23:00:30 +0200, Thomas Bleher wrote:
| application/x-tar-gztgz tar.gz
I think that this line should be added to the mime.types file.
Upstream Mutt mime.types has it. To add it to Debian or Ubuntu,
please see the package owning
package mutt
severity 384642 wishlist
close 384642
thanks
Hello Kurt, and thanks for the report.
On Friday, August 25, 2006 at 19:09:32 +0200, Kurt Roeckx wrote:
I'm using a latin1 terminal, but I've set up vim to use utf-8 files by
default, but fall back to latin1. Vim also shows latin1 on
Hi Kyle,
On Friday, August 25, 2006 at 20:28:46 -0400, Kyle Wheeler wrote:
Mutt degrades the charset to the weakest one necessary. In other
words, if the characters that you use in your file are all valid
iso-8859-1 characters, then mutt will treat the file as iso-8859-1.
This is generally
On Saturday, August 26, 2006 at 12:54:01 +0200, Kurt Roeckx wrote:
On Sat, Aug 26, 2006 at 11:47:47AM +0200, Alain Bench wrote:
I close this Debian bug as duplicate [of upstream/1317]
The proper way would be to set it as forwarded, since it's not
actually solved.
Humm... Really forward
On Saturday, August 26, 2006 at 11:02:55 +0200, Kurt Roeckx wrote:
vim is set up to try utf-8 first, and if it fails fall back to
iso-8859-1.
This Vim smart charset auto-sensing is a great feature, outside of
Mutt. For Mutt, by design, the $editor must be dumb, and use only the
charset of
Hello Kurt, James,
On Thursday, April 3, 2008 at 19:23:53 +0200, Kurt Roeckx wrote:
The termencoding should be based on the LCTYPE, and what locale
charmap or nl_langinfo(CODESET) returns. I see no reason why you ever
want this to be something else.
Exactly. That should have been The
package mutt
# works as designed
close 474506
thanks
Hello Martin, and thank you for the report.
On Sunday, April 6, 2008 at 11:52:46 +0200, Martin F. Krafft wrote:
If I decode-save or decode-copy a mail [...] the attachment are
removed in the copy. The attachment should stay.
The
Hello Jörg, and thanks for the suggestion.
On Sunday, April 6, 2008 at 14:06:06 +0200, Jörg Sommer wrote:
message/rfc822; mutt -R -f '%s'; edit=mutt -f '%s'; needsterminal
You should not put single-quotes around %s in mailcap. Mutt does
this for you, the right way, as should any other
91 matches
Mail list logo
