Linux

48665 readers

572 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

I don't understand this file pathing (lemmy.world)

submitted 17 hours ago by WereCat@lemmy.world to c/linux@lemmy.ml

5 comments fedilink hide all child comments

Hi, I'm trying the desktop Grayjay app and it seems to work fine.

I just have to keep locating the app in folder whenever I want to launch it so I found out how to make it appear in the GNOME Apps and launch it there.

However it requires me to copy 2 folders (cef,wwwroot) from the app folder into my "/home/werecat" folder and I don't understand why when it can launch just fine from the executable without me having to do that.

Any idea on what I'm missing or doing wrong? The main goal is to add the app to my Dash to Dock.

you are viewing a single comment's thread
view the rest of the comments

[–] WereCat@lemmy.world 2 points 7 hours ago (1 children)

Thanks, that actually worked even though it did not at first.

I've tried to also do export PATH=/home/werecat/Grayjay:$PATH but that did not work either. And finally I had to remove the TryExec for some reason for the Path to start working.

It launches now with Terminal even though I've set it to 'false' but at least it runs.

[–] Aiwendil@lemmy.ml 4 points 4 hours ago* (last edited 4 hours ago)

Just to make this clear (Sorry if it's unnecessary, but maybe still useful info for others)...Path= lines in .desktop files are not related at all to the $PATH environment variables. They do something completely different (And yes, picking Path as key was a terrible choice in my view). Path= lines in .desktop files change the current working directory...they do about the same as a cd <directory> in a shell.

They do not change where a .desktop file looks for executables....only indirectly if a executable runs another file relative to the current directory or looks for images/icons/audio/other data relative to the current working directory.

And I have no clue why it doesn't work with TryExec...the desktop file spec doesn't mention anything about that :( ( https://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html )