Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Did you launch nano by CLI? Your command history could go back far enough that the command may still be in there. A quick
history | grep nano
might be helpful here.You might also need to check the command history for the superuser account depending on whether and how you might have used
sudo
to access any privileged files. If you had a root shell open at the time, commands were likely logged to the history file in /root, so you may need to runsudo -s
and open a root shell before running thehistory | grep nano
command.sudo
seems not to take shell primitives as an argument, so `sudo history probably won't work.Good luck!
Oh man, i had no idea. Thank you, I'll check that out!