zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: Line number in multline editing buffer?
Date: Fri, 26 Sep 2014 22:00:48 -0700	[thread overview]
Message-ID: <140926220048.ZM6105@torch.brasslantern.com> (raw)
In-Reply-To: <20140926110002.1077e3a5@xs4all.nl>

On Sep 26, 11:00am, Joep van Delft wrote:
}
} I did not manage to find a way to determine the current line number
} in a multiline buffer (the one after a history operation, so without
} the $PS2)?

The line number should be given by

    $(( ${#LBUFFER//[^$'\n']/} + 1 ))

I leave it to you to hack up edit-command-line to pass that to your
editor in the proper way ...


  reply	other threads:[~2014-09-27  5:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  9:00 Joep van Delft
2014-09-27  5:00 ` Bart Schaefer [this message]
2014-09-27 20:26   ` Joep van Delft

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

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

  git send-email \
    --in-reply-to=140926220048.ZM6105@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).