LinuxGSM_ Dev
  • Home
  • Getting Started
    • Getting Started
    • Programming Language
    • Development Software
    • Test Environment
    • Developer Commands
    • Adding a new Game Server
  • Workflow
    • Semantic Versioning
    • Workflow
    • Agile
    • Pull Requests
    • Gitflow
    • Conventional Commits
    • Unit Tests
  • Technical
    • Main Executable
    • Commands
    • Exit Codes
    • Functions
    • Modules
      • Fixes
      • Core
    • Game Server Querying
    • Messages & Logs
    • Checks
    • Exit
    • Install
    • Debuggins
  • Code Standards
    • Style Guide
    • Shellcheck Linter
    • Text Editor Settings
Powered by GitBook
On this page
  • Indentation
  • Line Ending
  • Trailing White Spaces

Was this helpful?

  1. Code Standards

Text Editor Settings

[WIP] discuss using LF and white space remover etc.

PreviousShellcheck Linter

Last updated 1 year ago

Was this helpful?

Below is information on requirements needed when using a text editor to work on LinuxGSM code. All the recommended text editors can be set up to take into account the requirements.

Indentation

LinuxGSM uses tabs instead of spaces, it is possible to specify tabs and convert spaces to tabs if required.

Line Ending

All files must be saved using LF (Line Feed) line endings which is the line ending used by UNIX based systems. Please ensure that your text editor is saving in LF format as failure to do so will cause BASH scripts to stop functioning.

For more info about line endings check out the article "".

Trailing White Spaces

When developing code sometimes it can be easy to end up with trailing white spaces. as shown below.

fn_example_func(){
    # The line below has two spaces after its final character
    code••
}

All code must have whitespaces removed to keep code tidy. Many text editors have a feature that will automaticly remove trailing whitespaces when a file is saved. It is highly reccomended this feature is turned on.

The Great Newline Schism