From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacsuser@freemail.hu, 36970@debbugs.gnu.org
Subject: bug#36970: 26.2; invalid-read-syntax could print the location of the error
Date: Sun, 31 Jan 2021 16:57:54 +0200 [thread overview]
Message-ID: <831re1887h.fsf@gnu.org> (raw)
In-Reply-To: <87wnvttqlo.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 31 Jan 2021 10:14:59 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 31 Jan 2021 10:14:59 +0100
> Cc: 36970@debbugs.gnu.org
>
> Should the line/column numbers be based on what Fcount_lines return, or
> should they be the actual line number of the buffer? That is, taking
> selective display etc into consideration or not? Ignoring all that and
> just counting newlines would make sense in many situations (it's more
> like when compiling a file), but not in others?
>
> And... I'm slightly nervous about calling out to something as
> complicated as Fcount_lines.
What is Fcount_lines?
> So I was poking through the Emacs lisp code to see whether there's any
> function that will just tell me what line I'm on, and there's...
> display_count_lines in xdisp.c, but that doesn't really seem like a good
> fit, since that's in redisplay, and not lread.c context.
Can you tell why did you think display_count_lines will not do the job
you need it to do?
> Isn't there any function that will just return the line number at point?
That's display_count_lines, IMO.
next prev parent reply other threads:[~2021-01-31 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 8:27 bug#36970: 26.2; invalid-read-syntax could print the location of the error ndame
2021-01-30 7:54 ` Lars Ingebrigtsen
2021-01-31 9:14 ` Lars Ingebrigtsen
2021-01-31 10:15 ` Lars Ingebrigtsen
2021-01-31 14:57 ` Eli Zaretskii [this message]
2021-02-01 8:40 ` Lars Ingebrigtsen
2021-02-01 15:06 ` Eli Zaretskii
2021-02-01 16:10 ` Lars Ingebrigtsen
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=831re1887h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36970@debbugs.gnu.org \
--cc=emacsuser@freemail.hu \
--cc=larsi@gnus.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).