unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: bad mailer Subject meddling (was: links in Help buffer aren't always correct)
Date: Thu, 15 Dec 2005 07:39:25 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGEEMDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <u64prq8hx.fsf@gnu.org>

    -----Original Message-----
    Subject: Re: [drew.adams@oracle.com: links in Help
    bufferaren'talwayscorrect]

    Drew, could you please do something about your #$%^&* mailer? Look how
    it butchers the Subject lines when it thinks they are too long: it
    removes whitespace and splices words, which makes it a pain to read
    and use "C-c C-n" in Rmail.

Sorry, I don't know how to fix that in Outlook. I use Outlook 2000, for
various reasons related to work. It's old, but still a very common (the most
common?) email client in use. I don't defend it, but it's the one I use.

If it produces brain-dead subject lines, but it is a very common mailer,
maybe Rmail's C-c C-n could somehow deal with it by adding extra
intelligence to handle the retarded output ;-)?  No flames please - I don't
even know what C-c C-n does, and I'm not proposing that good, free programs
bend to the idiosyncrasies of bad MS products.  I can also try to remember
to edit the Subject line, to shorten it - but that will mess up sorting
messages by Subject. Another alternative is, sad to say, using the Delete
key on posts from Drew.

Another problem I noticed with Outlook, BTW, is that even if I set the
format explicitly to "plain text", when I reply to a Unicode post the result
appears formatted. In that case, at least, I found a workaround (provided I
notice it in time): explicitly change the encoding of the message from
Unicode.

On a related subject: Unlike the posts to emacs-devel, bug reports get the
original sender's email address (e.g. "[drew.adams@oracle.com]") prepended
to the subject line, as in this one (but I removed that). That makes the
subject much longer (m u c h  longer, in some cases). Is that "feature"
really necessary or a good idea?

  reply	other threads:[~2005-12-15 15:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13  3:15 [drew.adams@oracle.com: links in Help buffer aren't always correct] Richard Stallman
2005-12-13 17:17 ` Kevin Rodgers
2005-12-13 19:52   ` [drew.adams@oracle.com: links in Help buffer aren't alwayscorrect] Drew Adams
2005-12-13 23:53     ` Kevin Rodgers
2005-12-14 18:10       ` Kevin Rodgers
2005-12-14 20:02       ` Richard M. Stallman
2005-12-14 22:48         ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Drew Adams
2005-12-15  1:11           ` Kevin Rodgers
2005-12-15  2:01             ` [drew.adams@oracle.com: links in Help bufferaren'talwayscorrect] Drew Adams
2005-12-15  3:16             ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Stefan Monnier
2005-12-15 17:08             ` Richard M. Stallman
2005-12-15  4:39           ` Eli Zaretskii
2005-12-15 15:39             ` Drew Adams [this message]
2005-12-15 18:47               ` bad mailer Subject meddling (was: links in Help buffer aren't always correct) Alfred M. Szmidt
2005-12-16  5:08                 ` Richard M. Stallman
2005-12-16  7:55                 ` Eli Zaretskii
2005-12-15 19:43               ` Eli Zaretskii
2005-12-15 17:08           ` [drew.adams@oracle.com: links in Help buffer aren'talwayscorrect] Richard M. Stallman
2005-12-16 18:53             ` Kevin Rodgers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DNEMKBNJBGPAOPIJOOICGEEMDAAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).