Re: Suggestion for saving attachments

Re: Suggestion for saving attachments

[ShengHuo ZHU]

Christoph Conrad <christoph.conrad@gmx.de> writes:

> Hello ShengHuo,
> 
> i read about the following functionality in another mail/newsreader
> (can't remember the name...).
> 
> After saving an attachment the program optionally (by user-request)
> _replaces_ the attachment (or the content of the attachment) with the
> path to the saved attachment, something like:
> 
> - Attachment initially saved to "/home/cc/docs/foobar.txt" -
> 
> I think it would be fine to preserve the attachment itself, e.g. to
> replace the content of the attachment with this message.
> 
> This is a functionality i think it's very useful, cause the user often
> does not want to have two places where an attachment is stored,
> especially in the case of really big attachments. Often i want to work
> with a document received in an attachment and don't want to preserve the
> original document, but want to know where i saved the original document
> initially.

The functionality has been implemented, though only one part each
time.  To save and strip, press `C-o' on the MIME button, then an edit
buffer will show. If you are sure that Gnus has done the Right
Thing(TM), type `C-c C-c' to replace the part with a message/external-body.  
Of course, now Gnus inlines message/external-body.

ShengHuo

Re: Suggestion for saving attachments

[Christoph Conrad]

>>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:

    ZSH> The functionality has been implemented, though only one part

Great, thank you!

One problem with Filenames containing 8-Bit characters remains:

The filename: "äöüÄÖÜß-leeres-word.doc" after saving external:

Content-Type: message/external-body;
  name="~/tmp/\344\366\374\304\326\334\337-leeres-word.doc";
  access-type=LOCAL-FILE

Content-Type: application/msword
Content-ID: <u66m5jmhm.fsf@cli.de>
Content-Transfer-Encoding: binary

It is displayed exactly like seen above.

Mit freundlichen Grüßen / Best regards

i. A.
Christoph Conrad

-- 
CLI-GmbH,  Matthiashofstr. 28-30,  D-52064 Aachen
Fon: +49 241 47051-0  Fax: +49 241 47051-89 Web: http://www.cli.de
(defvar my-computer '((OS . "GNU Emacs") (system-type . gnu/linux))
	"Programming environment.")

Re: Suggestion for saving attachments

[ShengHuo ZHU]

Christoph Conrad <C.Conrad@cli.de> writes:

> >>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
>     ZSH> The functionality has been implemented, though only one part
> 
> Great, thank you!
> 
> One problem with Filenames containing 8-Bit characters remains:
> 
> The filename: "äöüÄÖÜß-leeres-word.doc" after saving external:
> 
> Content-Type: message/external-body;
>   name="~/tmp/\344\366\374\304\326\334\337-leeres-word.doc";
>   access-type=LOCAL-FILE
> 
> Content-Type: application/msword
> Content-ID: <u66m5jmhm.fsf@cli.de>
> Content-Transfer-Encoding: binary
> 
> It is displayed exactly like seen above.

Fixed.

ShengHuo

Re: Suggestion for saving attachments

[Christoph Conrad]

>>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:

    ZSH> Fixed.

It's getting better ;-)

Now the unprocessed contents look like:

Content-Type: message/external-body;
  name*=iso-8859-1''~%2ftmp%2f%e4%f6%fc%c4%d6%dc%df-leeres-word.doc;
  access-type=LOCAL-FILE

Content-Type: application/msword
Content-ID: <ud7gd9g6z.fsf@cli.de>
Content-Transfer-Encoding: binary

and the display looks like

[2. message/external-body; \201ä\201ö\201ü\201Ä\201Ö\201Ü\201ß-leeres-word.doc]...

where the "\201" in the my display is ONE character (0x81) displayed as
"\201".

Mit freundlichen Grüßen / Best regards

i. A.
Christoph Conrad

-- 
CLI-GmbH,  Matthiashofstr. 28-30,  D-52064 Aachen
Fon: +49 241 47051-0  Fax: +49 241 47051-89 Web: http://www.cli.de
(defvar my-computer '((OS . "GNU Emacs") (system-type . gnu/linux))
	"Programming environment.")

Re: Suggestion for saving attachments

[ShengHuo ZHU]

Christoph Conrad <C.Conrad@cli.de> writes:

> >>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
>     ZSH> Fixed.
> 
> It's getting better ;-)
> 
> Now the unprocessed contents look like:
> 
> Content-Type: message/external-body;
>   name*=iso-8859-1''~%2ftmp%2f%e4%f6%fc%c4%d6%dc%df-leeres-word.doc;
>   access-type=LOCAL-FILE
> 
> Content-Type: application/msword
> Content-ID: <ud7gd9g6z.fsf@cli.de>
> Content-Transfer-Encoding: binary
> 
> and the display looks like
> 
> [2. message/external-body; \201ä\201ö\201ü\201Ä\201Ö\201Ü\201ß-leeres-word.doc]...
> 
> where the "\201" in the my display is ONE character (0x81) displayed as
> "\201".

It works for me, but I heard about this kind of bug.  The problem
probably is related to the semi-obsolete way to display 8-bit
character.  If you have standard-display-8bit,
standard-display-european or so in your .emacs, replace them with
set-language-environment.

ShengHuo

Re: Suggestion for saving attachments

[Christoph Conrad]

Hello ShengHuo,

you wrote:

    > If you have standard-display-8bit, standard-display-european or so
    > in your .emacs, replace them with set-language-environment.

I did have a set-language-environment, but there were

;; (standard-display-8bit 160 255)
;; (standard-display-european 1)

I removed them, rebooted and there was no effect...

Best regards,
cu, -cc-
-- 
EMACS: Every Mode Accelerates Creation of Software
(defvar my-computer '((OS . "GNU Emacs") (system-type . gnu/linux))
	"Programming environment.")

Re: Suggestion for saving attachments

[ShengHuo ZHU]

Christoph Conrad <christoph.conrad@gmx.de> writes:

> Hello ShengHuo,
> 
> you wrote:
> 
>     > If you have standard-display-8bit, standard-display-european or so
>     > in your .emacs, replace them with set-language-environment.
> 
> I did have a set-language-environment, but there were
> 
> ;; (standard-display-8bit 160 255)
> ;; (standard-display-european 1)
> 
> I removed them, rebooted and there was no effect...

Are you using unibyte Emacs?

I've probably fixed the problem.

ShengHuo

Re: Suggestion for saving attachments

[Christoph Conrad]

Hello ShengHuo,

you wrote:

    > Are you using unibyte Emacs?

Yes.

    > I've probably fixed the problem.

I tested it, it's fixed.

Best regards,
cu, -cc-
-- 
EMACS: Every Mode Accelerates Creation of Software
(defvar my-computer '((OS . "GNU Emacs") (system-type . gnu/linux))
	"Programming environment.")