git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, code@khaugsbakk.name
Subject: Re: [PATCH v3] send-email: make it easy to discern the messages for each patch
Date: Sat, 06 Apr 2024 03:34:51 +0200	[thread overview]
Message-ID: <cd8ed09c0efa712aa93a45558bf6ad8e@manjaro.org> (raw)
In-Reply-To: <xmqqttkfqnvm.fsf@gitster.g>

On 2024-04-06 03:30, Junio C Hamano wrote:
> Dragan Simic <dsimic@manjaro.org> writes:
> 
>> According to my research, the "->ornaments(0)" call should work in
>> all environments as expected.  It's also officially documented. [1]
>> 
>> [1] https://perldoc.perl.org/Term::ReadLine#ornaments
> 
> Go back to the DESCRIPTION section and realize that it is a
> front-end for different implementations.  The functions are listed
> in separate sections, the first section being "Minimal set of
> supported functions", the other one being "Additional" that may or
> may not be available/effective for everybody.  Which side does
> ornaments fall in that page?

Well spotted, thanks.  Perhaps it's the best to leave the prompts
as-is until I spend some time to cover the possible Perl platform
and package differences properly.

Furthermore, it would be useful to add some color coding to the
produced outputs, so the failures and successes could be spotted
even more easily, but that's perhaps a can of worms that's best
if left unopened.


      reply	other threads:[~2024-04-06  1:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06  0:50 [PATCH v3] send-email: make it easy to discern the messages for each patch Dragan Simic
2024-04-06  1:12 ` Junio C Hamano
2024-04-06  1:17   ` Dragan Simic
2024-04-06  1:30     ` Junio C Hamano
2024-04-06  1:34       ` Dragan Simic [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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=cd8ed09c0efa712aa93a45558bf6ad8e@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=code@khaugsbakk.name \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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://80x24.org/mirrors/git.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).