Klipper

Command_Templates

English

Translate

Zen

	English	Actions
	This document provides information on implementing G-Code command sequences in gcode_macro (and similar) config sections.
	G-Code Macro Naming
	Case is not important for the G-Code macro name - MY_MACRO and my_macro will evaluate the same and may be called in either upper or lower case. If any numbers are used in the macro name then they must all be at the end of the name (eg, TEST_MACRO25 is valid, but MACRO25_TEST3 is not).
	Formatting of G-Code in the config
	Indentation is important when defining a macro in the config file. To specify a multi-line G-Code sequence it is important for each line to have proper indentation. For example:
	Note how the `gcode:` config option always starts at the beginning of the line and subsequent lines in the G-Code macro never start at the beginning.

Loading…

No matching activity found.

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Double space: Spanish, Spanish

Glossary

English	English
No related strings found in the glossary.

String information

Screenshot context

Screenshot 2021-06-21 at 09-12-20 KevinOConnor klipper-translations

Flags

md-text, read-only

String age

2 years ago

Last updated

12 months ago

Source string age

2 years ago

Translation file

docs/locales/en/LC_MESSAGES/Command_Templates.pot, string 1