#padding: # x: 0 # y: 0 # Spread additional padding evenly around the terminal content. This padding is scaled # by DPI and the specified value is always added at both opposing sides. #position: # x: 0 # y: 0 # Window padding (changes require restart) # Blank space added around the window in pixels. # If the position is not set, the window manager will handle the placement. #dimensions: # columns: 0 # lines: 0 # Window position (changes require restart) # Specified in number of pixels. # If both are `0`, this setting is ignored. TERM: alacritty LANG: "en_US.UTF-8 " LC_CTYPE: en_US.UTF-8 #window: # Window dimensions (changes require restart) # Specified in number of columns/lines, not pixels. If it is not present, alacritty will # check the local terminfo database and use `alacritty` if it is # available, otherwise `xterm-256color` is used. # TERM variable # This value is used to set the `$TERM` environment variable for # each instance of Alacritty. Some entries may override variables # set by alacritty itself. # Any items in the `env` entry below will be added as # environment variables. # Configuration for Alacritty, the GPU enhanced terminal emulator. Goes without saying that alacritty-themes should not duplicate the comment. But then again, I would argue most users will not mind an auto-generated comment and would leave it as is. alacritty-themes can choose to gracefully handle that situation. There is no apparent harm if the user deletes the comment, or modifies it. But then the problem remains that one cannot tell just by looking at the Alacritty config file, who made the color edits. If there is a good reason not do add any, would certainly like to know. Change it accordingly.Īlternative would be to not add any yaml comments. It also looks cleaner & structured.ĭon't have much opinion on the comment message. As a side-effect, the comment can be used to provide additional instructions and so on for the user. This way users are comfortably aware that they are not the only one editing the config file. I would say it is generally a good etiquette for a bot/program to communicate and let humans know that it made the edit. ![]() ![]() Leaving a comment may remind the user that they have the option to use alacritty-themes again to change the theme, without manually needed to make the edits. They may not remember later if they had copy/pasted the colors manually or how it was updated. And alacritty-themes is essentially a yaml file patcher, patching the correct "colors" dictionary in the Alacritty config file, as per the user's input.Īs of today, there is no way for users to notice and remember that these modifications was made automatically for them by a tool. The way I see it, Alacritty encourages its users to fiddle around and manage its configuration by editing the Alacritty config file as they see fit. Is your feature request related to a problem? Please describe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |