From: Drew Adams <drew.adams@oracle.com>
To: unfrostedpoptart <david@therogoffs.com>, help-gnu-emacs@gnu.org
Subject: RE: linum + narrow = hang
Date: Sat, 30 Jan 2016 18:08:54 -0800 (PST) [thread overview]
Message-ID: <58a5616e-a466-45b5-84e5-b13f770dc812@default> (raw)
In-Reply-To: <d69e28fa-cc77-48ec-8afe-3c8546402a22@googlegroups.com>
> emacs hangs if I try and narrow while linum is on. It displays
> Error in Post-command-hook (linum-update-current): (args-out-of-range 1 1)
> ...
> Any ideas?
`M-x report-emacs-bug'. Provide a step-by-step recipe to repro
the problem, starting with `emacs -Q'.
next prev parent reply other threads:[~2016-01-31 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 1:51 linum + narrow = hang unfrostedpoptart
2016-01-31 2:08 ` Drew Adams [this message]
[not found] ` <mailman.3223.1454206146.843.help-gnu-emacs@gnu.org>
2016-01-31 4:04 ` unfrostedpoptart
2016-01-31 16:14 ` Eli Zaretskii
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=58a5616e-a466-45b5-84e5-b13f770dc812@default \
--to=drew.adams@oracle.com \
--cc=david@therogoffs.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).