[BUG] -disable-history not working

[haennes]

Rofi version (rofi -v)

Version: 1.7.5+wayland3

Configuration

https://gist.github.com/haennes/9b100643da1e93aa4ea9845688002d83

Theme

https://gist.github.com/haennes/494f96e6a339701f9bb2422639d0c223

Timing report

No response

Launch command

rofi -dmenu -disable-history -no-fixed-num-lines -l 1 -i -input /dev/null -password -p "Passphrase:"

Step to reproduce

run rofi -dmenu -disable-history -no-fixed-num-lines -l 1 -i -input /dev/null -password -p "Passphrase:"

Expected behavior

doesnt write anything to $XDG_CACHE_HOME/rofi-entry-history.txt (i.e. ~/.cache/rofi-entry-history.txt)

Actual behavior

outputs a password to this file

Additional information

I actually am on wayland, but this is completely irrelevant for this bug

Using wayland display server protocol

• No, I don't use the wayland display server protocol

I've checked if the issue exists in the latest stable release

• Yes, I have checked the problem exists in the latest stable version

[DaveDavenport]

good catch, the entry history should also be disabled.

[haennes]

Sorry, but I have no clue on how to fix that myself.....
I tried but failed to understand the code structure :/

[DaveDavenport]

ill fix it when I have time.

[DaveDavenport]

commited code that should fix the code disabling it when -password is passed.
It also disables it with -disable-history.

[haennes]

doesnt fix it on my machine. Have actually confirmed i am using the right rofi using nix repl....
Behaviour is still the same as before.
I am not sure enough though, can you reproduce? (still same cmd as in original post)
This shouldnt have anything to do with me using wayland as it is such a core functionality (i am using this git repo as a source anyways), right?

[DaveDavenport]

you are not using this repository. you are using @lbonn his fork.

[trinitronx]

you are not using this repository. you are using @lbonn his fork.

Yes, the fixes will have to be merged into the lbonn/rofi fork from this repo (git merge upstream/next).

[jmonroynieto]

Would you consider creating a command to disable it once it is already running? A command to send a message to toggle which would be caught by the daemon could be fantastic. I am running it as a systemd service and having to kill it and then relaunch it is a bit of a friction point.

I envision a timer too. my use case involves fetching passwords from my manager, having it so that I don't have to toggle it back again sounds very appealing. I'm not a C developer so I can't offer a PR in any reasonable timeframe.

[DaveDavenport]

@jmonroynieto I don't understand your request in the context of rofi. But please make a new discussion on this (see guidelines!) , so we don't pollute this issue.