mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-25 08:35:56 +03:00
[GH-ISSUE #535] ec-probe monitor does not work on Linux (list goes downwards) #484
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#484
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @erkexzcx on GitHub (Aug 12, 2018).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/535
@hirschmann commented on GitHub (Aug 14, 2018):
I need some more info to reproduce this error. Which shell are you using? Have you tried a different shell? Have you tried disabling stuff like e.g. powerline?
@erkexzcx commented on GitHub (Aug 14, 2018):
I have not used ec-probe on linux in the past at all. I am currently using my own maintained nbfc-git package from AUR (for Arch Linux).
Because everything else seem to work just fine, I assume this needs to be fixed in code. Let me know if there is anything you would like me to provide.
P.S. You can check PKGBUILD if needed.
@hirschmann commented on GitHub (Aug 14, 2018):
The last time I tested it, it worked fine in bash for Manjaro and Ubuntu.
I will try to reproduce the issue with your AUR package.
@hirschmann commented on GitHub (Aug 14, 2018):
I have tested your AUR package and found the problem:
In the script you put at
/usr/bin/ec-probeyou pipe the output of ec-probe into sed which fucks up the formatting.@erkexzcx commented on GitHub (Aug 15, 2018):
That's my bad. I've fixed this issue now: https://aur.archlinux.org/packages/nbfc-git/
@erkexzcx commented on GitHub (Aug 15, 2018):
I created #537 as a result of this issue :) Thanks for your help, hirschmann!