unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Bourguignon <spam@mouse-potato.com>
Subject: Re: how do I know that the buffer is narrowed
Date: Wed, 30 Nov 2005 23:10:39 +0100	[thread overview]
Message-ID: <87vey9kcrk.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: mailman.17354.1133368063.20277.help-gnu-emacs@gnu.org

"mak kwak" <makwak@wp.pl> writes:
> Do You know if there is any buffer local variable that tells this to me ?

Yes, there are some buffer local variables, but they're in C!

DEFUN ("widen", Fwiden, Swiden, 0, 0, "",
       doc: /* Remove restrictions (narrowing) from current buffer.
This allows the buffer's full text to be seen and edited.  */)
     ()
{
  if (BEG != BEGV || Z != ZV)
    current_buffer->clip_changed = 1;
...


>From lisp, you could compare (point-min) and (point-max):

(defun narrowedp ()
  (not (equal (list (point-min) (point-max))
              (save-restriction (widen) (list (point-min) (point-max))))))


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
Our enemies are innovative and resourceful, and so are we. They never
stop thinking about new ways to harm our country and our people, and
neither do we. -- Georges W. Bush

       reply	other threads:[~2005-11-30 22:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.17354.1133368063.20277.help-gnu-emacs@gnu.org>
2005-11-30 22:10 ` Pascal Bourguignon [this message]
2005-11-30 22:41   ` how do I know that the buffer is narrowed Johan Bockgård
2005-11-30 23:10     ` David Kastrup
2005-12-01 11:31       ` Giorgos Keramidas
2005-12-01 12:12         ` David Kastrup
2005-12-01 12:44           ` Giorgos Keramidas
2005-12-01 16:52         ` Stefan Monnier
2005-12-01 18:41           ` Giorgos Keramidas
2005-12-04 12:13           ` Ehud Karni
     [not found]           ` <mailman.17838.1133698823.20277.help-gnu-emacs@gnu.org>
2005-12-04 14:54             ` Stefan Monnier
2005-11-30 16:27 mak kwak
2005-11-30 19:54 ` Kevin Rodgers

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=87vey9kcrk.fsf@thalassa.informatimago.com \
    --to=spam@mouse-potato.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).