unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Andy Stewart <lazycat.manatee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Strange problem with (setq buffer-read-only t).
Date: Fri, 16 Jan 2009 02:03:17 +0800	[thread overview]
Message-ID: <87prioe9ay.fsf@debian.domain> (raw)

Hi all,

I have develop irfc.el (interface for IETF RFC document) at:
http://www.emacswiki.org/emacs-en/irfc.el

I use (setq buffer-read-only t) in function `irfc-mode' for make RFC
buffer read-only.

And strange thing is, the (setq buffer-read-only t) that write in code looks
no effect.
But everything is okay if i eval (setq buffer-read-only t) after i open
RFC document.

Why not effect in my code?

So strange....

Andy idea?

Thanks.

  -- Andy





             reply	other threads:[~2009-01-15 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 18:03 Andy Stewart [this message]
2009-01-15 18:22 ` Strange problem with (setq buffer-read-only t) Juanma Barranquero
2009-01-16  1:04   ` Andy Stewart
2009-01-16  1:16     ` Juanma Barranquero
2009-01-16  1:29       ` Andy Stewart

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=87prioe9ay.fsf@debian.domain \
    --to=lazycat.manatee@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).