From: rnkn <rnkn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Manipulate cur in mscan (like in mless)
Date: Sun, 08 Dec 2024 12:11:17 +0100 [thread overview]
Message-ID: <20241208111117.6BD9E30A19@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-268@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Closed issue by rnkn on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/268
Description:
Hello!
Thank you for such wonderful software! It's such a joy to use :)
I have a feature request. I don't know how complicated it might be.
I would like to be able to navigate around `mscan` the same way I can in `mless`, and for this to change the current `cur`. It's essentially duplicating the exact functionality of `mless` but without the message preview.
What do you think?
**Edit**: `cur` not `seq`
prev parent reply other threads:[~2024-12-08 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 5:09 [ISSUE] Manipulate mseq " rnkn
2024-12-07 17:09 ` Manipulate cur " leahneukirchen
2024-12-08 7:47 ` rnkn
2024-12-08 11:11 ` rnkn
2024-12-08 11:11 ` rnkn [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241208111117.6BD9E30A19@inbox.vuxu.org \
--to=rnkn@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).