search

savedra1 / clipse

Configurable TUI clipboard manager for Unix
MIT License
216 stars 7 forks source link

Private Mode #54

Open maydayv7 opened 1 month ago

maydayv7 commented 1 month ago

It would be nice if a 'Private Mode' feature would be implemented. When turned on (maybe using a keybinding), entries shouldn't be copied to the clipse history, but only to the buffer

It could also be an alternative to #21 if implementing app-specific behaviour isn't feasible

savedra1 commented 1 month ago

Heya @maydayv7 thanks for your suggestion.

Could what you're describing not already be achieved with a command like clipse -kill; sleep 60 && clipse -listen ? This could also be held in a script that takes an arg for how long to sleep for also and bound to a key just as easily.

Because of the above I'm unsure if this would be worth the engineering effort. I think the auto-forget should be possible as there are some go libraries for retrieving window names etc. Thinking to allow users to add a list of window names to exclude/make temporary into the config file - What do you think?

maydayv7 commented 1 month ago

Yeah that's the temporary workaround that I'm currently using to emulate the behaviour, and I guess it works fine so ;)

Probably the only real issue would be to indicate in the UI when the background listener process is not running, otherwise one may run clipse -kill and use the UI normally for previous entries but may forget to run clipse listen again (in case timeout isn't hardcoded, like a keybinding to toggle clipse)

savedra1 commented 1 month ago

@maydayv7 I've started liking the sound of it tbh. In terms of engineering effort it would be quite simple to add a cmd like clipse -pause 5m or something similar that will execute that subcommand with nohup and add a "paused" identifier in the TUI.

I'm gonna keep this open for implementation at some point :smile:

maydayv7 commented 1 month ago

Noice lmao

Also please consider pausing indefinitely (like a toggle)