From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fish-shell: update to 3.4.0.
Date: Mon, 21 Mar 2022 15:07:16 +0100 [thread overview]
Message-ID: <20220321140716.zJ1JtriQVvRRJnfhzpl_oQBJ7Ych0-DlQdt03XsyEOI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36121@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
New comment by mhmdanas on void-packages repository
https://github.com/void-linux/void-packages/pull/36121#issuecomment-1073942094
Comment:
@paper42 well, not strictly all users it seems. From https://fishshell.com/docs/current/cmds/fish_title.html:
> This requires that your terminal supports programmable titles and the feature is turned on.
I'm not sure about this, but it probably also wouldn't affect those who have a custom `fish_title` function (as shown in the example in the URL above). However, it's not like we know how many Fish users aren't affected, so it may be safe to assume that the majority _will_ face that error.
next prev parent reply other threads:[~2022-03-21 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 11:04 [PR PATCH] " mhmdanas
2022-03-14 23:15 ` zen0bit
2022-03-14 23:15 ` zen0bit
2022-03-14 23:31 ` mhmdanas
2022-03-14 23:31 ` mhmdanas
2022-03-15 16:37 ` mhmdanas
2022-03-19 16:59 ` Vistaus
2022-03-20 22:26 ` paper42
2022-03-21 14:07 ` mhmdanas [this message]
2022-03-21 14:12 ` paper42
2022-03-24 19:12 ` Chocimier
2022-03-24 19:15 ` mhmdanas
2022-03-26 10:36 ` [PR PATCH] [Updated] " mhmdanas
2022-03-26 10:37 ` fish-shell: update to 3.4.1 mhmdanas
2022-03-29 17:42 ` [PR PATCH] [Merged]: " Chocimier
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=20220321140716.zJ1JtriQVvRRJnfhzpl_oQBJ7Ych0-DlQdt03XsyEOI@z \
--to=mhmdanas@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).