0rax / fishline Goto Github PK

what does "^^ /dev/null" mean?

im finding this in https://github.com/0rax/fishline/blob/master/segments/__flseg_git.fish

but i notice this code has been checked in long time ago, and im only getting errors recently in the last month, in OSX

The Project documentation says the following to install using fisher

fisher add 0rax/fishline

but on fisher version 4.3, there is no such option as add and only install. The following commands only brings in just fishline.fishand nothig else.

% fisher -v
fisher, version 4.3.1

% fisher install 0rax/fishline
fisher install version 4.3.1
In config.fish /home/GSS
Fetching https://codeload.github.com/0rax/fishline/tar.gz/HEAD
Installing 0rax/fishline
           /home/shiva/.config/fish/functions/fishline.fish
Installed 1 plugin/s

Creating a fish prompt as below

function fish_prompt
    fishline -s $status
end

results in the following

__fishline_segment_close: command not found
~/.config/fish/functions/fishline.fish (line 71): 
    __fishline_segment_close
    ^
in function 'fishline' with arguments '-s 0'
	called on line 2 of file ~/.config/fish/functions/fish_prompt.fish
in function 'fish_prompt'
in command substitution

Let me know what I am missing. Thanks for your work.

We are still relatively new in town, and just getting started, but we are more stable than the other options, namely OMF. I think some of these functions could be turned into a handful of Wahoo plugins or maybe some could be even make it to core. We are always accepting feature request and feedback. I would love if you could give Wahoo a look.

Regards 😄

Awesome,love it. Here is my setting:
fisher install 0rax/fishline
function fish_prompt
fishline -s $status FULLPWD N ARROW
end
funcsave fish_prompt
function fish_right_prompt
fishline -s 0 -r GIT USERHOST
end
funcsave fish_right_prompt
set FLCLR_FULLPWD_BG brcyan
`

But the left powerline is line one, then my prompt on line 2, then right is on line 2 as well. How do I get right to be on line 1?

The wiki need an update before merging dev branch to master to create v2.0.0 of fishline (PR #14).

• The Segments section it will require:
  • the addition of the SIGSTATUS segment
  • the addition of the missing segments SPACE and JOBS
• Update of the Configuration section:
  • explain the new way to configure fishline
  • note on backward compatibility and how it was working in v1
• Update Installation Guide with links to how to configure and a basic usage of the fishline function

Currently, the USERHOST segment uses the output of hostname. If called with no options, hostname will default to printing the fully qualified domain name (like hostname -f). The domain component is omitted (hostname -s) on Linux (GNU/Glibc?) systems.
A quick check on the FreeBSD manpage for hostname shows that it also defaults to using the -f flag.

I suggest using ('hostname -s') to unify the behavior across systems, since that i what most users would likely expect/want the segment to do. Another option would be to make the flag configurable, though I do not see much demand for an option to clutter the screen with the FQDN every time.

Fisher 4.1.0 has been released, which removed add and rm commands. add has been replaced by install. The README.md should be updated. See: https://github.com/jorgebucaran/fisher/releases/tag/4.1.0

Also, since 4.0.0, Fisher introduced a new way to organize plugins. All plugin files should be put under completions, conf.d and functions directories. They have deprecated init.fish as well. See: https://github.com/jorgebucaran/fisher/releases/tag/4.0.0

Currently, simply running fisher install 0rax/fishline will not install fishline successfully.

Update Segments section with:

• Customizable symbols for each segments
• Cleaner description

It seems that I don't have any of the fonts for the symbol (ie: the write lock symbol etc) and I was just wondering which font you were using for those. Thanks for this by the way, works great.

Are you guys interested by using fishline as a fish_right_prompt.

I made some test, and I dont know. I am not a fan of right prompt to be honest but I imagine that having the GIT or CLOCK segment at the right of a one line fishline setup (Without the N segment)
with it vanishing when you are too close could be a good idea.

Here is my test:

If you wanna test it youself here is the little code I used:

#!/usr/bin/env fish
# -*-  mode:fish; tab-width:4  -*-
function fish_right_prompt

    set_color yellow
    printf "\uE0B2"
    set_color black -b yellow
    printf " %s " (date "+%H:%M:%S")
    set_color normal -b normal

end

Thank you.

Hello again. I'm running urxvt on AwesomeWM. After installing Fish_Line I get a crash any time I try to resize more than a few pixels.

Would you consider making your script compatible with cygwin installations? Unfortunately powerline has horrible performance on windows and I'm looking for an alternative.

This is what is currently output after installing fishline:

Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
fish: Unknown command 'tput'
/home/sijpj/.config/fish/fishline/segments/n.fish (line 8):     tput el
                                                                    ^
in function 'FLSEG_N',
        called on line 78 of file '/home/sijpj/.config/fish/fishline/fishline.fish',

in . (source) call of file '-',
        called on line 111 of file '/home/sijpj/.config/fish/fishline/fishline.fish',

in function 'fishline',
        called on line 15 of file '/home/sijpj/.config/fish/config.fish',
        with parameter list '0'

in function 'fish_prompt',
        called on standard input,

in command substitution
        called on standard input,

I've tried both the master and dev branches.

the current init.fish causes duplicate entries to be added to $fish_function_path when running nested fish instances or if the config.fish file doesnt have guards against running in non-interactive mode. This causes functions not to autoload on linux (works fine in macOS). While this is probably also a bug in fish, it should probably be fixed here to avoid cluttering environment variables

Not an issue. Just want to send appreciation for the work that went into this. I love my prompt!

Thank you!

I just switched to Ubuntu 16.04 which uses procps-ng `kill' instead of util-linux.

The kill -l function doesn't work and instead prints the signals. The only way to get the list is to use kill --list=<sig{num,name}> but the util-linux kill doesn't work like that. Also the procps-ng kill doesn't understand signals > 128 so a CTRL-C which results in SIGINT 130 (signal #2) would error. The procps-ng `kill' is bad and not adherant to POSIX.

I found this http://stackoverflow.com/questions/29377995/find-signal-number-by-signal-name but I'm not sure what a good solution is, or if the solution is just to use util-linux `kill' which would require system modification.

But at the very least, expecting kill -l to work and for signals > 128 is an assumption which apparently is untrue.

The screenshot looks awesome. Good job!

This project would gain even more track if you could port it to oh-my-fish as a theme or theme-switcher plugin.

What do you think?

P.S: One thing I don't like about line themes though is that they don't work well with Terminal.app so I need to rely on iTerm2 of which I am not very fond of.

Powerline has just a single line, with all the info before where you type, rather than having a newline with an arrow where you type. How can I replicate that here?

Hi, I couldn't find this documented anywhere, so I'm not sure if this is a bug in fishline, the respective terminals or simply something that could be documented better.

Most terminals look like this (gnome-terminal):

But a few look like this (BlackBox):

The gnome-builder integrated terminal is also affected:

One correlation is that the working terminals seem to be installed normally, while (so-far) the affected terminals are installed as flatpaks. I believe I also noticed similar behaviour on windows (msys2 and wsl2), but will need to double check next time I'm on a windows machine. So perhaps there's something weird going on in flatpak and windows environments?

Does fishline do any checks to decide if it'll render [ ] instead of arrows?

Update Development section with:

• Small style guide
• How to create test for your segments
• Internal symbols that might be modified by a theme