Shameless plug: I am the author.

you are viewing a single comment's thread
view the rest of the comments
[+] 115 points 2 years ago* (last edited 10 months ago) (5 children)
  • [–] 25 points 2 years ago (2 children)

    That's what happens when you don't set $GOPATH I think

  • source
  • parent
  • hideshow 4 child comments
  • [–] 51 points 2 years ago (1 child)
  • [–] 10 points 2 years ago (1 child)

    It makes it insofar better to me that you have the option to change it. You can't change Mozilla programs to use anything but .mozilla (apart from modifying the source code of course) so for me seeing the folder is at least a way of telling me that the variable is unset.

    The better question is which folder is suited the best to store the stuff that goes into $GOPATH

  • source
  • parent
  • hideshow 2 child comments
  • [–] 11 points 2 years ago* (1 child)

    Go pisses me off with that. I separate projects the way I want but go wants every project written in go in one big directory?

  • source
  • parent
  • hideshow 2 child comments
  • [+] 2 points 2 years ago* (last edited 10 months ago) (1 child)
  • [+] -1 points 2 years ago (1 child)
  • [–] 15 points 2 years ago (1 child)

    What I want in $HOME are the following directories:

    If I’m on a GUI-based environment:

    • Desktop
    • Documents
    • Downloads

    In general:

    • .local
    • my_junk_folder_i_made

    I’d like everything else to live within something like ~/.local thanks

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 years ago* (3 children)

    Maybe Linux should have .local and .roaming folders like Windows. local = only useful on this system, roaming = good to sync across systems. Config would be in .roaming if it's not machine-specific.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 5 points 2 years ago (1 child)

    Does ~/.config fit the bill for the second one?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 years ago* (last edited 2 years ago)

    There's some stuff in~/.config that's specific to the computer. KDE is a good example - a lot of KDE apps mix config and state in the same file. There's some solutions for syncing these files, like https://github.com/VorpalBlade/chezmoi_modify_manager which is an addon to Chezmoi that can exclude particular keys when storing an INI-style config file in Git.

    I'm sure there's some config files in there that are entirely specific to the computer. Things like the Wayland per-monitor scaling settings are in there somewhere I think.

    There's also things like data files that you may want to keep in sync across machines. They're not really configs.

  • source
  • parent
  • [–] 1 point 2 years ago (1 child)

    There is a .local folder these days.

    Profile roaming hasn’t been solved aside from NFS mounts. I guess Syncthing might work.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago*

    I know .local exists - My comment was more about .roaming which would be nice to exist, but doesn't currently exist.

    Profile roaming hasn’t been solved aside from NFS mounts. I guess Syncthing might work.

    I'm using Chezmoi to sync some dotfiles, scripts, etc. to a Git repo and that seems to work well enough for me. I'm not syncing much yet, though.

  • source
  • parent