unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Large text files - no line numbers ?
Date: Fri, 6 Dec 2019 13:56:01 -0500	[thread overview]
Message-ID: <20191206135601.310690ec@mistral> (raw)
In-Reply-To: <jwveexhuxtj.fsf-monnier+emacs@gnu.org>

On Fri, 06 Dec 2019 13:16:10 -0500
Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> Line numbers shouldn't affect bookmarks at all, so this is likely a
> red herring.

Could very well be.  The main subject is about the display of L??.
Then I noticed that bookmarks on that file did not work.  So maybe by
having the correct line number being displayed ...  It's all
assumption.  Maybe I should have started another thread in retrospect.

> How do you set the bookmarks?  How do you "go back" to them?
> What happens between the two operations?  Where do they go instead of
> where you wanted (they are not supposed to go back to "a line" but to
> a buffer position instead)?

C-x r m for setting.  I always give a name to the bookmark.  Then
bookmark-bmenu-list to show them and cursor or mouse to select one.

I always delete the existing ~/emacs.d/boomarks file before doing any
tests.  Or erase the current ones if they were not saved.

In the 733K log file, I go to line # 423 and set a bookmark named
'test1'.  Then I scroll further down to line # 536 and set a 'test2'
bookmark.  Jumping to the first bookmark will jump to the last one.
Jumping to the last one will jump tot he last one.

Setting a 3rd bookmark named 'test3' at line # 762 makes all bookmarks
jump to that line/location.

Do you think there's a possibility that some other lisp code in
the .emacs file could interfere with the bookmarks behaviour ?
Through time I have copy/pasted some useful snippets found here and
there.




  reply	other threads:[~2019-12-06 18:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 14:47 Large text files - no line numbers ? jonetsu
2019-12-04 14:57 ` Robert Pluim
2019-12-04 15:07   ` jonetsu
2019-12-04 15:49     ` jonetsu
2019-12-04 15:31   ` Eli Zaretskii
2019-12-05 14:44     ` jonetsu
2019-12-05 14:50       ` Stefan Monnier
2019-12-05 15:03         ` jonetsu
2019-12-06 18:16           ` Stefan Monnier
2019-12-06 18:56             ` jonetsu [this message]
2019-12-06 19:08               ` Stefan Monnier
2019-12-06 19:46                 ` jonetsu
2019-12-05 14:56       ` Robert Pluim
2019-12-05 15:27         ` jonetsu
2019-12-05 15:22       ` Eli Zaretskii
2019-12-05 15:46         ` jonetsu
2019-12-05 16:40           ` Eli Zaretskii
2019-12-05 17:56             ` jonetsu

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=20191206135601.310690ec@mistral \
    --to=jonetsu@teksavvy.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).