From: stacyharper <stacyharper@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: LESSKEYIN instead of LESSKEY ?
Date: Tue, 28 Sep 2021 21:09:21 +0200 [thread overview]
Message-ID: <20210928190921.O73xqZbxro94WiGgh_c-jWj-w4u6NtCtfblYYU9VzRs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-215@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
New comment by stacyharper on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/215#issuecomment-929545308
Comment:
Yes that will works. Thanks again for those fast fixes !
Btw, I added personal exit code handling with dedicated less quit
commands. I think we could find a way to give the hand to the user.
Without requiring to fork all the script.
prev parent reply other threads:[~2021-09-28 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 6:53 [ISSUE] " stacyharper
2021-09-28 7:02 ` stacyharper
2021-09-28 9:47 ` leahneukirchen
2021-09-28 10:24 ` stacyharper
2021-09-28 14:05 ` leahneukirchen
2021-09-28 16:18 ` stacyharper
2021-09-28 16:24 ` [ISSUE] [CLOSED] " leahneukirchen
2021-09-28 16:25 ` leahneukirchen
2021-09-28 19:09 ` stacyharper [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=20210928190921.O73xqZbxro94WiGgh_c-jWj-w4u6NtCtfblYYU9VzRs@z \
--to=stacyharper@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).