Skip to content

Unable to set default extension #152

Open

Description

@bkgrrl00

I am trying to set the default extension to *.TXT. I have tried each of the settings below, but none of them works. When I save a new file, the extension is either not set at all, or it is set to JSON.

{
"default_extension": "txt",
}

{
"default_extension": "Text",
}

{
"default_extension": ".txt",
}

{
"default_extension": "*.txt",
}

{
"default_extension": "Plain Text (*.txt)",
}

Activity

  1. skuroda commented on May 11, 2016

    @skuroda
    Contributor

    Hi @bookgrrl, where are you putting the file? I just tested by placing

    {
        "default_extension": ".txt"
    }
    

    In Packages/User/AdvancedNewFile.sublime-settings

  2. bkgrrl00 commented on May 11, 2016

    @bkgrrl00
    Author

    @skuroda The file is in C:\Users\[username]\AppData\Roaming\Sublime Text 3\Packages\User

  3. skuroda commented on May 21, 2016

    @skuroda
    Contributor

    Apologies, thought I responded to this. Are there any errors in the ST console after trying to enter a path? Is it always happening or only sometimes? The only thing I can think of is that the logic I have there removes the extension if it there's a . in the name.

  4. bkgrrl00 commented on May 22, 2016

    @bkgrrl00
    Author

    Hi Scott,

    Apologies for not getting back to you earlier. I don't get an error when I enter a path in the ST console, and the filename does not have a . in the filename, so I'm not sure what could be wrong. I decided to stop spending time troubleshooting ST since there are plenty of other text editors that do what I am looking for. For now, I am using Q10, which saves files as .txt by default and which displays the word count in the status bar.

    Maria

    Date: Fri, 20 May 2016 19:08:48 -0700
    From: notifications@github.com
    To: Sublime-AdvancedNewFile@noreply.github.com
    CC: bookgrrl@hotmail.com; mention@noreply.github.com
    Subject: Re: [skuroda/Sublime-AdvancedNewFile] Unable to set default extension (#152)

    Apologies, thought I responded to this. Are there any errors in the ST console after trying to enter a path? Is it always happening or only sometimes? The only thing I can think of is that the logic I have there removes the extension if it there's a . in the name.

    —
    You are receiving this because you were mentioned.
    Reply to this email directly or view it on GitHub

  5. mingyEx commented on Jul 24, 2022

    @mingyEx

    I modified my config file following the path mentioned here:

    // line99
         // String containing the default file extension. Note the extension is only applied
         // if the specified path does not contain a dot (.) character.
         "default_extension": ".txt",

    It worked, but the last few days it doesn't work again, the newly created files still don't get any suffix added, what am I doing wrong?

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions