From: Steven L Baur <steve@miranova.com>
Subject: Re: sgnus-0.32 + tm-7.41.1 == problems
Date: 01 Feb 1996 12:00:30 -0800 [thread overview]
Message-ID: <m2lommke8x.fsf@miranova.com> (raw)
In-Reply-To: Kai Grossjohann's message of 01 Feb 1996 10:23:23 -0800
>>>>> "Kai" == Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de> writes:
Kai> Hi all,
Kai> I'm trying to use these two together and notice a couple of problems
Kai> with composing a MIME message. I'm not sure whether they are due to
Kai> tm or due to sgnus, but I thought maybe a few of you use that
Kai> combination, too, and can tell me something about it.
Kai> When I hit C-c C-c from a *Gnus Mail* buffer, the Gcc copy is not
Kai> translated before being written to disk.
This is a new bug since it used to work a few versions back. Note
that after sending the mail your *Gnus Mail* buffer is correctly
formatted. So it's a timing problem of some sort.
Kai> I circumvent this problem by hitting C-c C-x C-z first, then typing
Kai> C-c C-c. This, however, invokes mail-send-and-exit rather than
Kai> gnus-mail-send-and-exit (the keybinding code in tm-edit seems to do
Kai> strange things which don't seem to do the right thing right here).
C-c C-x C-z is totally broken, but except for the behavior described
above, C-c C-c does The Right Thing.
Kai> Also, about signatures: When you use tm together with sgnus, it seems
Kai> that there are about five different packages all doing something with
Kai> signatures, and I have to turn them all off to get my own signature
Kai> handling (which is a one-line function that calls insert...)! I know
Kai> that this is not a bug, but it sure is inconvenient.
Yes. And they all work slightly differently too. I believe this was
supposed to be fixed with the Gnus posting styles additions (I'm way
behind catching up with the latest features :-( ).
Kai> Basically, tm seems to be a fine package (I like the automatic preview
Kai> stuff).
Yes. I especially like what I've seen with the inline graphics.
I would add to the current glitch list the problem with Emacs 19.30
and font-lock (or maybe lazy-lock). After sending mail or news the
buffer you are returned to gets its fonts and colors wiped out.
XEmacs is unaffected, and tm through 7.41.2 exhibits the problem.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
next prev parent reply other threads:[~1996-02-01 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-01 18:23 Kai Grossjohann
1996-02-01 20:00 ` Steven L Baur [this message]
1996-02-02 9:42 ` Kai Grossjohann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lommke8x.fsf@miranova.com \
--to=steve@miranova.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.
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 NNTP newsgroup(s).