Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
Cc: Norman Walsh <ndw@nwalsh.com>
Subject: Buffer read only?
Date: Fri,  4 Dec 1998 10:33:55 -0500	[thread overview]
Message-ID: <2311-Fri04Dec1998103355-0500-ndw@nwalsh.com> (raw)

I've just switched to NT Emacs 20.3.1 and pgnus 0.63.

I typically read mail and news with gnus.  I have an external process
that slurps up my mail and deposits it in ~/.incoming/mail.spool.
Then I use 'C-u 2 g' to snarf it into gnus.

With my new setup, gnus reads and splits the mail, then reports
 
   buffer is read only #<buffer *Group*>

I (setq debug-on-error t) and didn't get a traceback.  

If I exit gnus and return, all my mail shows up.

Bug or operator error?

--norm

P.S. Since I'm already sending a message...

- Is there any easy way to swap the functionality of "g" and "C-u 2 g"?

- All the lines in my group buffer end with ^M in Emacs 20.3.1.  Anyone
  got a hint about fixing that (I haven't tried yet)?

                                        Cheers,
                                          norm
-- 
Norman Walsh <ndw@nwalsh.com>      | My problems start when the smarter
http://nwalsh.com/                 | bears and the dumber visitors
                                   | intersect.--Steve Thompson,
                                   | wildlife biologist at Yosemite
                                   | National Park



             reply	other threads:[~1998-12-04 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-04 15:33 Norman Walsh [this message]
1998-12-04 16:00 ` Kai.Grossjohann
1998-12-04 16:05 ` ^M removal (Re: Buffer read only?) Karl Kleinpaste
1998-12-04 16:50   ` Norman Walsh
1998-12-04 17:17     ` Karl Kleinpaste
1998-12-04 17:48       ` Norman Walsh

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=2311-Fri04Dec1998103355-0500-ndw@nwalsh.com \
    --to=ndw@nwalsh.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).