Again, there was a large update. This time i saw a warning to remove something, or else i would break manjaro on restart.
Because I was having a terrible day, I forgot to remove that thing, and so i broke manjaro again.
However, before that happened, hours before, i did highlight what i was told to delete, and I copied it with CTRL+C.
This means that the broken thing that needs to be destroyed is in my copy-paste history.
I can access the command line with the standard CTRL+ALT+F2.
All i need is to find my copy-paste history. How can i find that file in the directory?
I do not know what specific clipboard manager I have. I thought it came default with Manjaro. Its logo is a paperclip, and it usually is pinned to the taskbar at the bottom of my screen.
OR, if you know what i need to delete anyway, and can just tell me the command to delete it, i will accept that too.
Well, in theory, if you have internet in the tty, you can sudo pacman -S xsel xclip and play with them like shown here and here for example.
But in reality, the clippboard does not survive reboot so it is lost.
Unless you have enabled history file, then you can cat ~/.cache/xfce4/clipman/textscr
I cannot remember if it was enabled by default but you can try.
If you issued a single command
whether you copy/pasted it or whether you just typed it
it will be in the shell’s history file
I’m not familiar with zsh - but it seems you are using Xfce4
in which case the shell is Bash (unless you explicitly changed it)
If the shell is Bash, you can recall your command history with the command: history
The file where this information is stored is: ~/.bash_history
and you can just as well just look at the contents of that file by opening it in an editor or, for example like this: less ~/.bash_history
and then just scroll through down to the most recent entries.
With zsh, the command should be the same, just the file name is different: ~/.zhistory
I believe - but I don’t know.
Except that he is not looking for a command but a text he copied.
Anyways, if the clipman cache is empty or it does not help it will be a good idea to start a new topic to try to solve the actuall boot issue, because this here is kind of XY Problem.
