Skip to content

Expand ~ from config #7051

Closed
Closed

Description

@ForteDexe

Is there an existing issue for this?

  • I have searched the existing issues

OS/Web Information

  • Web Browser: Vivaldi
  • Local OS: Ubuntu 24.10
  • Remote OS: Ubuntu 24.10
  • Remote Architecture: amd64
  • code-server --version: 4.93.1 69df011 with Code 1.93.1

Steps to Reproduce

  1. add this user-data-dir: ~/.config/code-server-data to config.yaml
  2. run command code-server

Expected

~/.config/code-server-data

Actual

But in the web browser, it will be:

~/~/.config/code-server-data

Note

I get it now, depends on where the current directory in the terminal is, code-server will use the current directory plus user-data-dir

Activity

  1. added
    bugSomething isn't working
    triageThis issue needs to be triaged by a maintainer
    on Oct 25, 2024
  2. code-asher commented on Oct 29, 2024

    @code-asher
    Member

    ~ is normally expanded by the shell, so it would not get expanded in a YAML config. But, it would be nice if we manually expand it when we read the config.

  3. changed the title [-]Ubuntu config.yaml user-data-dir, duplicate '~'[/-] [+]Expand `~` from config[/+] on Oct 29, 2024
  4. added
    enhancementSome improvement that isn't a feature
    and removed
    bugSomething isn't working
    triageThis issue needs to be triaged by a maintainer
    on Oct 29, 2024
  5. ForteDexe commented on Nov 2, 2024

    @ForteDexe
    Author

    If run as the services, using ~ it recognizes the user-data folder well
    But other stuff might not, ie:

    [error] Unable to read file '/~/.config/code-server-user-data/extensions/extensions.json' (Error: Unable to resolve nonexistent file '/~/.config/code-server-user-data/extensions/extensions.json'): Error: Unable to read file '/~/.config/code-server-user-data/extensions/extensions.json' (Error: Unable to resolve nonexistent file '/~/.config/code-server-user-data/extensions/extensions.json')
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementSome improvement that isn't a feature

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions