From xemacs-m  Sat Feb 15 10:20:06 1997
Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA04549
	for <xemacs-beta@xemacs.org>; Sat, 15 Feb 1997 10:20:04 -0600 (CST)
Received: (from hniksic@localhost)
          by jagor.srce.hr (8.8.5/8.8.4)
	  id RAA05397; Sat, 15 Feb 1997 17:20:00 +0100 (MET)
Sender: hniksic@public.srce.hr
To: xemacs-beta@xemacs.org
Subject: line-move-ignore-invisible
X-URL: ftp://gnjilux.cc.fer.hr/pub/unix/util/wget/
X-Attribution: Hrv
X-Face: &}4JQk=L;e.~x+|eo]#DGk@x3~ed!.~lZ}YQcYb7f[WL9L'Z*+OyA\nAEL1M(".[qvI#a2E
 6WYI5>>e7'@_)3Ol9p|Nn2wNa/;~06jL*B%tTcn/XvhAu7qeES0\|MF%$;sI#yn1+y"
From: Hrvoje Niksic <hniksic@srce.hr>
Date: 15 Feb 1997 17:19:59 +0100
Message-ID: <kig7mka82j3.fsf@jagor.srce.hr>
Lines: 22
X-Mailer: Gnus v5.4.12/XEmacs 19.14

I've always been iritated by `next-line' and co. being stuck in Gnus
invisible headers.  So, though I, The Day had come -- I decided to
hack next-line.  Meditating on the inner and outer nature of extents,
text-properties, overlays, I loaded (`found'?) prim/simple.el.

There I looked at the source, and see that they both call line-move.
Excellent!  So only line-move needs to be hackified.  And moving
towards line-move -- lo! what do I see?

(defvar line-move-ignore-invisible nil
  "*Non-nil means \\[next-line] and \\[previous-line] ignore invisible lines.
Outline mode sets this.")

I set this to t, and it works like a charm.  Is *that* all it takes?
It looks that way.  Now, I'd like to know *why* doesn't this variable
default to t?  The same variable is also set to nil in GNU Emacs, but
then again, in GNU Emacs you don't get stuck in headers.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Ask not for whom the <CONTROL-G> tolls.

