> I am pleased to say the next release of fish is on its way.
>
> As usual, we are starting with a beta release, 3.1b1. Testing on all
> platforms is greatly appreciated.
Hi. In Cygwin x86_64, the build fails with a bunch of "narrowing conversion
from int to wchar_t" errors:
[51/113]
> After installing cygwin and fish in it, you can change the default shell
> with this method:
>
> https://superuser.com/questions/940529/how-to-change-the-default-shell-in-cygwin#answer-1134672
>
> Unless it has changed since October 2016: I have not used Cygwin for a
> long time...
Yes, any
> > The next release of fish is on its way! I know it has been delayed a
> > number of weeks. A new arrival in my family has altered the schedule
> > somewhat!
>
> Wonderful! Congratulations to all.
>
> > As usual, we are starting with a beta release, 2.7b1. Testing on all
> > platforms is
> The next release of fish is on its way! I know it has been delayed a
> number of weeks. A new arrival in my family has altered the schedule
> somewhat!
Wonderful! Congratulations to all.
> As usual, we are starting with a beta release, 2.7b1. Testing on all
> platforms is greatly appreciated.
> See issue https://github.com/fish-shell/fish-shell/issues/4220
>
> Is there a reason to continue allowing `read` with no var name(s) to store
> the result of the read?
It's not clear from the manual what read even does if you don't give it any
variable names. Does it discard the input line? Is
> I've been using fish for about 6 months now after moving from zsh.
>
> Everything was going well, until recently git sub-command completions have
> slowed down to to point of being unusable.
Yeah. I haven't tried to debug this, but it was so slow that I just disabled git
completions:
touch
What's the best (simplest, most efficient, or however) way to compare two
version strings in fish? Any better way than writing a custom function?
For example, I want to test if the current running version of fish is less than
2.3.1. I want to compare $FISH_VERSION to 2.3.1, using the version
At http://fishshell.com, under Release History it says that 2.3.0 was released
on April 22. But as the Release Notes show, it was released on May 20. Andrew
--
Mobile security can be enabling, not merely restricting.
Hi,
On Cygwin using the default notifier gives errors when I have multiple
shells running. I have been changing the code in
env_universal_common.cpp to make the shmem_polling strategy the
default. It works fine, but it would be nice to not have to do it since
it's the last local
Due to the large number of architectural and other changes within fish,
we have started with a beta release - fish 2.2b1. Any testing would be
very much appreciated.
Hi. I'm testing in Cygwin x86_64. fish 2.2b1 builds and runs fine there.
However, whenever I start a subshell, I get an error
(not sure if I have enough beer)
I've moved some of my stuff from fish back to bash for several reasons.
But, the biggest was probably going box to box and having inconsistent
setups.
However, I've stabilized my personal work flow a bit, and I want to start
using (and committing) to it
How hard was it to build? Do you have destructions? I figure I might as
well be using source for when/if I find issues :)
Not hard. It builds OOTB, but I added a few small patches, to add
Cygwin-specific completions and make a few Cygwin-specific changes to
/etc/fish/config.fish. For that
On trunk, universal variables no longer require fishd (!) and so it doesn't
get launched. This was first enabled with commit 20d7a142, and will be the
default behavior in the next release.
When the release announcement comes, I hope there will be a short
description of why this was done and
If you really don't want fishd running, then you probably don't want to be
using fish.
I wouldn't go that far. IIUC all fishd is responsible for is universal
variables. fish has lots of other desirable features, and you won't get
cleaner syntax by adding onto bash.
I have fish (2.1.1) set as my default login shell now on my Ubuntu (14.04.1)
host.
Mostly it works fine, but when I ssh into the host to run a command, so fish
runs
non-interactively, I get a bunch of errors:
andrex@helium ~ ssh helium w
set_color: Could not set up terminal
set_color: Could not
On Thu, 9 Oct 2014, Andrew Schulman wrote:
I have fish (2.1.1) set as my default login shell now on my Ubuntu
(14.04.1) host.
Mostly it works fine, but when I ssh into the host to run a command, so
fish runs
non-interactively, I get a bunch of errors:
andrex@helium ~ ssh helium w
Part of the fish philosophy is it's not in fish if it's somewhere else
I know I'm new here, but at the risk of already wearing out my welcome, I
don't completely agree with that approach.
Everything in fish is already somewhere else. Taken to its extreme, it's
not in fish if it's somewhere
Hi. New fish user, and first post here.
What's the recommended way to do regular expression testing and matching in
fish? The test function doesn't support regexes. I could use expr, for
example:
if expr $var : 'a(.)b(.)'
then
# do something with the match
end
but that's awkward,
external tools, that does what
I need.
On Thu, Oct 2, 2014 at 2:32 PM, Andrew Schulman and...@utexas.edu wrote:
Hi. New fish user, and first post here.
What's the recommended way to do regular expression testing and matching in
fish? The test function doesn't support regexes. I could use
19 matches
Mail list logo
