unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: netjunegg <netjunegg@outlook.com>
To: Drew Adams <drew.adams@oracle.com>,
	'Andreas Schwab' <schwab@linux-m68k.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: with text file including very long lines, line number field of mode line becomes "??"
Date: Mon, 3 Dec 2012 01:23:38 +0000	[thread overview]
Message-ID: <BAY002-W181D03905F6BC5C782A869CB7400@phx.gbl> (raw)
In-Reply-To: <9F44291DA6EB4DA49F00F796FBAC0893@us.oracle.com>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

Thank you very much. It works. 
I knew line-number-display-limit but didn't know line-number-display-limit-width.

> From: drew.adams@oracle.com
> To: schwab@linux-m68k.org; netjunegg@outlook.com
> Subject: RE: with text file including very long lines,	line number field of mode line becomes "??"
> Date: Fri, 30 Nov 2012 08:47:30 -0800
> CC: emacs-devel@gnu.org
> 
> > See line-number-display-limit and line-number-display-limit-width.
> 
> Maybe the popup menu over the line number could have an item that takes you to
> the doc for those vars when `??' is displayed: (emacs) `Optional Mode Line'.
> 
> IOW, `??' says only "No idea what the line number is".  It could help to also
> point users to info on how to control/fix this.
> 
> And/or a popup item could just increase the limit to make it big enough to show
> the number of the last line number for the current buffer.
> 
> 
 		 	   		  

[-- Attachment #2: Type: text/html, Size: 1282 bytes --]

      reply	other threads:[~2012-12-03  1:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30  0:38 with text file including very long lines, line number field of mode line becomes "??" netjunegg
2012-11-30 11:13 ` Andreas Schwab
2012-11-30 16:47   ` Drew Adams
2012-12-03  1:23     ` netjunegg [this message]

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=BAY002-W181D03905F6BC5C782A869CB7400@phx.gbl \
    --to=netjunegg@outlook.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).