/usr/bin/emacs: No such file or directory...yet it exists
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Try to start emacs with the full path: /usr/bin/emacs
If that works bash will probably know next time where to find emacs. I think you can als do 'hash -r' to force bash making a new hash table.
ahh okay, yeah, I already tried /usr/bin/emacs. But...if the absolute path wouldn't work, would hash -r work either? It seems like it's illogical that it wouldn't be designed to work with an absolute path to the file. I'm home for the weekend now, we'll see when I get back.
Yeah, could be. When I tried Ubuntu AMD64, it couldn't writing to the drives properly and quickly reported filesystem errors (I'm using SATA drives, by the way.)
I'd start backing up, then once you have any important data off the disk then start playing around with e2fsck to see if you cna fix the filesystem errors if that's the root cause.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.