2018-12-30 07:06:27 -05:00
|
|
|
# 1.5.2: Procrastination in progress
|
2018-12-27 13:48:40 -05:00
|
|
|
|
2021-08-14 07:03:16 -04:00
|
|
|
Rofi 1.5.2 is another bug-fix release in the 1.5 series.
|
2018-12-30 06:58:59 -05:00
|
|
|
|
2018-12-27 13:48:40 -05:00
|
|
|
|
|
|
|
## Fix border drawing
|
|
|
|
|
|
|
|
Issue: #792, #783
|
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
There turned out to be a bug in how borders are drawn. It would overlap parts of the border on corners, screwing up
|
|
|
|
transparency.
|
|
|
|
|
|
|
|
![broken border](border-issue.png)
|
2018-12-27 13:48:40 -05:00
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
This is now fixed.
|
2018-12-27 13:48:40 -05:00
|
|
|
|
|
|
|
## Improve Icon handling
|
|
|
|
|
|
|
|
Issue: #860
|
|
|
|
|
|
|
|
Several bugs around Icon handling have been fixed:
|
|
|
|
|
|
|
|
* Failing to load multiple (identical icons) on initial load.
|
|
|
|
* Preload user-set icon theme.
|
2018-12-30 06:58:59 -05:00
|
|
|
* Use the common threadpool in rofi for the icon fetching, instead of spawning a custom one.
|
|
|
|
|
|
|
|
|
|
|
|
## New sort syntax
|
2018-12-27 13:48:40 -05:00
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
Because of all the changes to the sorting methods in rofi, the command-line options for it where very confusing.
|
|
|
|
To fix this they have been changed.
|
|
|
|
|
|
|
|
The `sort` option is now used to enable/disable sorting. (This can also be changed at run-time using the hotkey)
|
|
|
|
|
2019-03-04 18:15:41 -05:00
|
|
|
The `sorting-method` allows you to set the sorting method. Currently it supports **normal** (levenshtein) and **fzf**.
|
2018-12-27 13:48:40 -05:00
|
|
|
|
|
|
|
## Documentation updates
|
|
|
|
|
|
|
|
Issue: #879, #867, #837, #831, #804
|
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
Thanks to all the people highlighting or providing fixes to the documentation.
|
|
|
|
|
2018-12-27 13:48:40 -05:00
|
|
|
## Improving the ssh known hosts file parser
|
|
|
|
|
|
|
|
Issue: #820
|
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
The original known hosts parser was very limited. The parser has been extended to a bit more robust.
|
|
|
|
|
2018-12-27 13:48:40 -05:00
|
|
|
## Additions
|
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
For some reason I can never make a release without adding more features to it. (Feature creep?).
|
|
|
|
|
2018-12-27 13:48:40 -05:00
|
|
|
### Option to change the negate character
|
|
|
|
|
|
|
|
Issue: #877
|
|
|
|
|
|
|
|
The option to negate a query: `foo -bar` e.g. search for all items matching `foo` but not `bar` caused a lot of
|
|
|
|
confusion. It seems people often use rofi to also add arguments to applications (that start with a -).
|
|
|
|
|
|
|
|
To help with this, the negate character (`-`) can be changed, or disabled.
|
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
To disable:
|
|
|
|
|
|
|
|
```
|
|
|
|
rofi -matching-negate-char '\0'
|
|
|
|
```
|
|
|
|
|
2018-12-27 13:48:40 -05:00
|
|
|
|
|
|
|
### Modify the DRUN display string
|
|
|
|
|
|
|
|
Issue: #858
|
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
An often requested feature is the ability to change the display string for the drun modi.
|
|
|
|
The `-drun-display-format` option is added that allows just this.
|
|
|
|
|
|
|
|
> -drun-display-format
|
2021-08-14 07:03:16 -04:00
|
|
|
>
|
2018-12-30 06:58:59 -05:00
|
|
|
> The format string for the drun dialog:
|
|
|
|
> * name: the application's name
|
|
|
|
> * generic: the application's generic name
|
|
|
|
> * exec: the application's executable
|
|
|
|
> * categories: the application's categories
|
|
|
|
> * comment: the application comment
|
2021-08-14 07:03:16 -04:00
|
|
|
>
|
2018-12-30 06:58:59 -05:00
|
|
|
> Default: {name} [({generic})]
|
|
|
|
|
|
|
|
Items between `[]` are only displayed when the field within is set. So in the above example, the `()` are omitted when
|
|
|
|
`{generic}` is not set.
|
|
|
|
|
|
|
|
|
|
|
|
### Theme format now supports environment variables
|
2018-12-27 13:48:40 -05:00
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
You can use environment variables as part of your theme/configuration file property value.
|
|
|
|
Environment variables start with `$` and the name is surrounded by `{}`.
|
|
|
|
So to query the environment `FOO` you can do:
|
2018-12-27 13:48:40 -05:00
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
```css
|
|
|
|
#window {
|
|
|
|
background: ${FOO};
|
|
|
|
}
|
|
|
|
```
|
2018-12-27 13:48:40 -05:00
|
|
|
|
2018-12-30 06:58:59 -05:00
|
|
|
The environment is then parsed as a normal value.
|