ph111p / powerline Goto Github PK

I swap between keyboard layouts pretty often, and i'd like to see an indicator for it on Powerline, i know there exists a segment for lock status, is there a possibility for Layout indicator as well? setxkbmap -query might be a good wrapped command for this

Beispiel: CPU Segment nur anzeigen, wenn mehr als 50% CPU verwendet werden.

Make segments separate, so that they just have to register with the bar.

That way users can install only the segments they need. And adding new segments is easier and needs no update to the powerline..

The upstream source seems to be quiet on maintenance. I made a ticket there:

powerline#2012

If the current maintainer, @Lokaltog, was willing to share responsibilities, would you be willing to takeover/share maintenance responsibilities with them?

I have the issue that the activeWindowTitle-segment is cutted at the half of the window although it has some space to the right. I see two fixes:

• make shrinking optional
• only shrink if both sides collide (if no middle segment is used)

Best,
Philip

Currently we have to specify all icons for each i3 mode.

We should instead have one file specifying the icons mapped to windows. And then override some of these in specific modes.

Scenario 1:
2 workspaces (with fancy fontawesome icons):
1  web
2  term
Scenario 2:
2 workspaces (without fancy fontawesome icons):
1web
2term

Scenario 1:
I click on 2  term (to go to it), but it sends me to a new workspace called '2'
Same with 1  web, but instead it goes to '1'
Scenario 2:
I click on 2term, but it sends me to '2t'
Same with 1web, but instead it goes to '1w'

I could just change my workspaces names but :/

Also, extra question how to disable window icons?

Using the bar for longer times makes it have a noticeable delay when switching workspaces.

Some systems have this delay initially.

After migrating from powerline/powerline to PH111P/powerline, my tmux config breaks (I get the tmux' default green bar).

When using powerline-lint, the script fails, but still shows 'found duplicate key':

Traceback (most recent call last):
  File "/home/fliife/bin/powerline-lint", line 13, in <module>
    sys.exit(check(args.config_path, args.debug))
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/__init__.py", line 450, in check
    find_all_ext_config_files(search_paths, 'themes'),
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/__init__.py", line 379, in find_all_ext_config_files
    'type': subdir,
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/__init__.py", line 335, in updated_with_config
    hadproblem, config, error = load_json_file(d['path'])
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/__init__.py", line 327, in load_json_file
    config, hadproblem = load(F)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/__init__.py", line 16, in load
    r = loader.get_single_data()
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/constructor.py", line 48, in get_single_data
    return self.construct_document(node)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/constructor.py", line 57, in construct_document
    for dummy in generator:
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/constructor.py", line 252, in construct_yaml_map
    value = self.construct_mapping(node)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/constructor.py", line 205, in construct_mapping
    return BaseConstructor.construct_mapping(self, node, deep=deep)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/constructor.py", line 19, in f
    return gen_marked_value(func(self, node, *args, **kwargs), node.start_mark)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/constructor.py", line 140, in construct_mapping
    'found duplicate key', key_node.start_mark
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/lint/markedjson/loader.py", line 24, in echoerr
    echoerr(*args, **kwargs)
TypeError: echoerr() takes exactly 0 arguments (4 given)

I installed powerline through yaourt -S powerline-i3-git

Here is my theme, and here is my colourscheme. These are my defined colours.

Please note that this config works fine with the classic powerline

Also, important note, the default theme and colourscheme doesn't work either.
Somehow, I was able to get something like hl() has unknown argument click (something like that), but I fail to reproduce this error message. I'll let you know if I manage to find the exact message

EDIT: The exact error I described above is the following:

Traceback (most recent call last):
  File "/home/fliife/bin/powerline-config", line 22, in <module>
    args.function(pl, args)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/commands/config.py", line 15, in
__call__
    self.function(*args, **kwargs)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/bindings/config.py", line 211, in tmux_setup
    init_tmux_environment(pl, args, set_tmux_environment=ste)
  File "/home/fliife/local/lib/python2.7/site-packages/powerline/bindings/config.py", line 125, in init_tmux_environment
    set_tmux_environment(varname, powerline.renderer.hlstyle(**highlight)[2:-1])
TypeError: hlstyle() got an unexpected keyword argument 'click'

It can be obtained by running powerline-config tmux setup

We should have a command to copy all config files to the appropriate place to allow editing, as out of the box the bar is not working for most installations.

We should be able to see all segments and their config. Preferably locally on the machine.

This should also display the current settings with all infered defaults.

It would be nice to have the events "enter" and "exit" for an segment.
Background: I would like to show conky on enter and close conky on exit so conky would show up while hovering.

For example the media player segment crashes if no google play libs are found. It should detect that and disable itself.

Powerline is not compatible with python3.4 anymore because of the file renderer.py.

Python 3.4 throws an exception (SyntaxError) on this line (and two other very similar ones)

contents_highlighted = self.hl(self.escape(contents_raw), **segment['highlight'], **segment)

Commenting out these lines make powerline work again, but segements are empty.

This can probably be easily fixed by passing bg=, fg=, attrs= instead of using parameter expansion (**segment['highlight'])

The weather segment is displaying an erroneous leading 5 when using Fahrenheit and a trailing 2 when using Celsius .

Having multiple monitors means Lemonbar renders multiple times on the currently active monitor.

This seems totally random and not intended.

Hi Philip,

the bars are quite often shown on the same monitor if I have two monitors. I.e., there is one monitor with two bars directly above each other and one monitor without a bar.

Best, Philip

this seems to be a bug till now.

Liste an Workspaces angeben, die vor allen anderen Workspaces in einer definierten Reihenfolge einsortiert werden.

Currently the wireless device name is hardcoded. We should instead detect this automatically and f.e. show the best connected device. Or one segment per device.

Clicking on the wireless segment should allow a binding to f.e. networkmanager to select a wifi network.

This means the wireless segment should be shown all the time.

Storing imap user and password in plain text is not recommended.

Also many users have thunderbird open anyway. So we could grap customizable counters from there instead of requesting everything twice. This would also allow multiple email accounts.

fuzzy time currently only works in english. we should be able to select different languages

like the wifi-segment

Is the cpu usage segment gone ? I can't seem to find it in the docs, and the one in my config simply stopped working.

Are there reasons for this ?

Also, I've always wondered, would it be difficult to add a shell command segment ? That would be really nice, as it would allow for very easy custom segments (and for cpu usage too !)

Since all configs are json, we could add a web based config editor that supports rearanging and adding new segments.

That would help find all these arcane config options you need to ask the devs about all the time.

Some segments have changing size (like cpu% f.e.)

This moves the whole bar all the time. So we should be able to pad these changing segments to stop them from moving.

When installing through pip with pip install powerline-status-i3, pip installs something which is somwhat close to this repo, but not exactly it..
This method will create /usr/lib64/python3.4/sites-packages/powerline containing standard powerline (what ?), and /bin/powerline-lemonbar.py, which has a different content than the content of this repo's scripts/powerline-lemonbar. Also, note the .py extension.

I tried using --no-cache-dir too.

Fix

Installing with pip install git+https://github.com/PH111P/powerline.git@develop works. I think it would be acceptable just changing this in the README

Bei folgender Konfiguration wird ein leeres Segment (wahrscheinlich für den heart-Bereich, der leer ist) links von dem Blitz/der Batterie angezeigt. Das hat vor einem der letzten Updates funktioniert.

{
   "function": "powerline.segments.common.bat.battery",
   "args": {
       "gamify": true,
       "steps": 0,
       "online": "",
       "full_heart": "",
       "half_heart": "",
       "empty_heart": "",
       "offline": "",
       "bat": 0
   }
}

We should allow small config files for individual segments and later just reference to these segments.

This would also allow multipart segments combining multiple single segments.

With this the bar config file could be significantly smaller.