unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T. V. Raman" <raman@users.sf.net>
To: monnier@iro.umontreal.ca
Cc: miles@gnu.org, raman@users.sf.net, emacs-devel@gnu.org
Subject: Re: Emacs CVS And VM Breakages
Date: Thu, 14 Feb 2008 19:50:35 -0800	[thread overview]
Message-ID: <18357.3083.656921.140261@gargle.gargle.HOWL> (raw)
In-Reply-To: <jwvodajoa1p.fsf-monnier+emacs@gnu.org>

Well, Iwas reporting a breakage. I didn't assert it shouldn't be
broken; on the other hand, how would you know that it was broken
if no one told you?

>>>>> "Stefan" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
    >> In general things felt sufficiently broken to cause me to
    >> roll back.
    Stefan> Well, this *is* "in development bleeding edge" code,
    Stefan> 
    Stefan> 
    Stefan>         Stefan
    Stefan> 
    Stefan> 
    >>>>>> "Miles" == Miles Bader <miles.bader@necel.com> writes:
    Miles> "T. V. Raman" <raman@users.sf.net> writes:
    >>>> I reverted to CVS version of Feb 1, and all of the
    >>>> problems I reported earlier e.g. VM losing the body of a
    >>>> message on sending have disappeared.
    Miles> 
    Miles> The internal representation of non-ASCII text in Emacs
    Miles> has changed (it is now based on a superset of utf8,
    Miles> rather than the old "emacs-mule" encoding).
    Miles> 
    Miles> My recollection (from years past though) is that VM
    Miles> has historically been a bit flaky about handling
    Miles> non-ASCII text, so it's not surprising such a change
    Miles> would expose bugs in VM.  I'd suggest contacting the
    Miles> VM maintainer.
    Miles> 
    Miles> -Miles
    Miles> 
    Miles> -- Witch, n. 1, an ugly and repulsive old woman in a
    Miles> wicked league with the Devil; 2, a beautiful and
    Miles> attractive young woman in wickedness a league beyond
    Miles> the Devil.
    Stefan> 
    >> -- 
> Best Regards, --raman
    Stefan> 
    Stefan>       
    >> Email: raman@users.sf.net WWW:
    >> http://emacspeak.sf.net/raman/ AIM: emacspeak GTalk:
    >> tv.raman.tv@gmail.com PGP:
    >> http://emacspeak.sf.net/raman/raman-almaden.asc Google:
    >> tv+raman IRC: irc://irc.freenode.net/#emacs
    Stefan>

-- 
Best Regards,
--raman

      
Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs




      reply	other threads:[~2008-02-15  3:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 14:29 Emacs CVS And VM Breakages T. V. Raman
2008-02-13  2:42 ` Miles Bader
2008-02-14 14:17   ` T. V. Raman
2008-02-14 15:03     ` Stefan Monnier
2008-02-15  3:50       ` T. V. Raman [this message]

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=18357.3083.656921.140261@gargle.gargle.HOWL \
    --to=raman@users.sf.net \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).