Package Details: fish-git 2:3.7.0.r1420.g776895274-1

Git Clone URL: https://aur.archlinux.org/fish-git.git (read-only, click to copy)
Package Base: fish-git
Description: User friendly shell intended mostly for interactive use.
Upstream URL: http://fishshell.com
Keywords: shell
Licenses: GPL2
Conflicts: fish, fish-shell
Provides: fish, fish-shell
Submitter: SanskritFritz
Maintainer: SanskritFritz (akiirui)
Last Packager: akiirui
Votes: 69
Popularity: 0.32
First Submitted: 2010-11-17 22:27 (UTC)
Last Updated: 2024-02-07 08:21 (UTC)

Dependencies (11)

Required by (81)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »

<deleted-account> commented on 2012-06-09 04:16 (UTC)

Same problem as delluminatus I'll try delluminatus's solution.

SanskritFritz commented on 2012-06-08 23:28 (UTC)

delluminatus: I don't get this history.1 error, sorry. On the other hand I modified the PKGBUILD in such a way that it can be compiled more times.

<deleted-account> commented on 2012-06-08 17:53 (UTC)

I get the following error on installation: /bin/sh: line 4: help_doc/man/man1/history.1: No such file or directory It can be fixed by manually creating the file "./src/fishfish/help_doc/man/man1/history.1". However, if you try to run makepkg again after manually changing the src tree, the build process substitutes "python2" for "python" a second time resulting in files referencing "python22." Basically I solved this problem by: echo "history.1 contents" > src/fishfish/help_doc/man/man1/history.1 then perform a re-substitution: find -wholename "./src/*.py" | xargs sed "s/python2/python/" -i Alternatively, you could alter the PKGBUILD by changing the three substitutions in the build() function to the following: sed -i "s/python[^2]/python2/" "internalize_scripts.py" sed -i "s/python[^2]/python2/" "make_completions.py" sed -i "s/python[^2]/python2/" "create_wajig_completions.py"

SanskritFritz commented on 2012-06-08 12:06 (UTC)

Added python2 as makedepend, thanks miffe.

SanskritFritz commented on 2012-06-06 12:06 (UTC)

Ahah, thanks, will be fixed soon.

miffe commented on 2012-06-06 11:58 (UTC)

I get this when building: /usr/bin/env: python2: No such file or directory make: *** [builtin_scripts.h] Error 127 Adding python2 to makedepends solves it.

<deleted-account> commented on 2010-12-23 21:11 (UTC)

Haven't yet stumbled upon any unexpected login-issues using fish. The biggest problem is that some commands expect you to be able to source standard shell scripts or output. e.g from 'dircolors', 'gpg-agent' and others... luckily most of them is just to "export <somevar>=<someval>" and can quite easy be converted to fish syntax. You can get to a jump start by browsing through my fish config files repo here: https://github.com/esodax/fishystuff Not much in there really, but feel free to extract what you want, or just to get an overall idea on how to solve 'source this-and-that' problems you might encounter yourself. Also, my way might not be the best way, but it works for me at least :) For example, "include/colors.fish" and "functions/run_gpg-agent.fish" resolves the problem I mentioned above with dircolors and the gpg-agent. And, again an extra thanks to SanskritFritz. Merry Christmas fish lovers! (sorry, couldn't access the ml from here)

<deleted-account> commented on 2010-12-23 10:11 (UTC)

@esodax: I'm trying to pick fish again while using (very little) of zsh. Can you write something more about issues when using fish as login shell? (you can reply to fish ml) Sincerely, Gour

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »