emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: divya@subvertising.org
Cc: emacs-orgmode@gnu.org
Subject: Re: [FEATURE] On line-numbers inside Org Babel Source Blocks.
Date: Sat, 10 Aug 2024 15:15:23 +0000	[thread overview]
Message-ID: <87sevc76k4.fsf@localhost> (raw)
In-Reply-To: <afb5b33004fbef035c47c2b2560552b4@subvertising.org>

divya@subvertising.org writes:

> I've been using Org Mode for literate programming purposes, and would
> like to have line-numbers within `src` blocks. I am able to export the
> Org buffer and get the line-numbers, but I am unable to do the same
> with regards to just in Org buffers. I am aware of `org-edit-special`,
> but I would rather appreciate if I can just look at a piece of code
> and know how long it is. I believe a header argument can be useful in
> toggling this.

I agree that it would be nice to have line numbering in code blocks.

> Since the source blocks can already implement syntax highlighting,
> font and other means of interacting with displaying Babel source
> blocks, theoretically this shouldn't be that difficult to implement?
> I'd be glad to help implementing this feature, if I can be slightly
> guided on where to refer to look for in the codebase.

AFAIK, it is not very easy. Syntax highlighting is just a matter of
applying the right text properties, but not line numbers.

Native line numbering in Emacs is implemented on low level, and is not
very exposed to Elisp. There is a limited set of options available for
customization - all in `display-line-numbers' variable. See "16.24
Customization of Display" section in Emacs manual.

I do not know anything built-in that can help in our situation, with
line numbers to be applied selectively.

We may try the approach taken by the old linum-mode, except that linum
is infamous for its poor performance. So, it might be better to hack on
https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/nlinum.el?h=externals/nlinum
as suggested in lisp/obsolete/linum.el commentary.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  parent reply	other threads:[~2024-08-10 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 13:59 [FEATURE] On line-numbers inside Org Babel Source Blocks divya
2024-08-09 21:30 ` Divya
2024-08-10 15:15 ` Ihor Radchenko [this message]
2024-08-11  9:50 ` Phil Estival

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sevc76k4.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=divya@subvertising.org \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).