unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mark Elston <m.elston@advantest-ard.com>
Subject: Re: Emacs and Read-Only Files
Date: Wed, 18 Oct 2006 11:11:03 -0700	[thread overview]
Message-ID: <12jcr9o4pa88oe1@corp.supernews.com> (raw)
In-Reply-To: <12jcqsch3k6ms6d@corp.supernews.com>

One other thing I noticed - when I look at the *Messages*
buffer I get the following messages:

   Note: file is write protected
   Loading semantic-c...done
   byte-code: Buffer is read-only: #<buffer abc.cpp>
   Loading semantic-edit...done
   Loading semanticdb-file...done
   Mark set

However, I commented out the loading of the cedet code (and the
ecb that requires it) and I still get the same issue.

Mark

* Mark Elston wrote (on 10/18/2006 11:03 AM):
> I have GNU Emacs 23.0.0.1 and GNU Emacs 22.0.50.1 compiled for
> Windows.  Both versions behave strangely when loading files
> that are Read-Only.
> 
> In both cases the file gets loaded, I get a message saying
> 'Mark Set' but the window doesn't switch to the newly loaded
> file.  This doesn't happen when I load a file with write permission.
> 
> Unfortunately (or fortunately), when I start up emacs with
> --no-init this behavior doesn't occur.
> 
> I have a rather extensive .emacs file and would *really* hate to
> go through the cycle of commenting out blocks and re-starting
> necessary to track this down.
> 
> So, does anyone have any ideas what could be happening?  Obviously,
> something I have loaded is interfering with the loading of these
> read-only files, but I don't have a clue what it could be.
> 
> Mark

  reply	other threads:[~2006-10-18 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 18:03 Emacs and Read-Only Files Mark Elston
2006-10-18 18:11 ` Mark Elston [this message]
2006-10-18 18:47   ` Mark Elston
2006-10-19  4:10     ` Barry Margolin
2006-10-19 17:37       ` Mark Elston

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=12jcr9o4pa88oe1@corp.supernews.com \
    --to=m.elston@advantest-ard.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 read-only IMAP folder(s) and NNTP newsgroup(s).