X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.9 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: i_bv0HaswBBqrACeSLu_1E5b From: michael AT mauger DOT com To: cygwin AT cygwin DOT com Cc: kbrown AT cornell DOT edu Subject: Re: Emacs 24.2.90.1 (previous-line) behavior Date: Tue, 22 Jan 2013 21:38:21 -0500 Message-ID: <1evfw1s1v4y.fsf@LT-MMAUGER.office.techtarget.com> MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > I've never seen this problem. Can you give a recipe for reproducing it > starting with `emacs-nox -Q'? > > > Ken $ emacs-nox -Q (you are placed in the *scratch* buffer) RET RET RET (opens some more blank lines) (Note that C-p and C-n work as expected) M-X linum-mode (Linum mode enabled. Line numbers appear in the left margin) C-n ... (Move to the end of the buffer) C-p ... (Move usually jumps up 2 lines at a time) I haven't seen this behavior in any development build in the last couple years (I rebuild from emacs/trunk every couple of weeks) and I enable linum-mode in all prog-mode derived modes (and some others). -- Michael -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple