eXo Wiki - Recent changes [en]

Batch Conversion Limitations

Parricc — Sat, 25 Apr 2026 17:06:58 GMT

← Older revision		Revision as of 10:06, 25 April 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	For batch files to successfully convert into bash files for Linux and MacOS, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.		For batch files to successfully convert into bash files for Linux and MacOS, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.

	=== Indenting nested if statements and for loops is necessary. ===		=== Indenting multi-line nested if statements and for loops is necessary. ===
	With the limitations of tooling, nested statements that written without indentation will fail to convert.		With the limitations of tooling, nested statements that written without indentation will fail to convert. <u>Each indentation should be specifically 2 or 3 spaces.</u> Avoid tabs.

	Example that fails to convert:		Example that fails to convert:
Line 14:		Line 14:
	</pre>		</pre>

	Instead, anything that is nested should have spacing to indicate the level of nesting. ~~The~~ closing parentheses ~~are~~ especially important.		Instead, anything that is nested should have spacing to indicate the level of nesting. Correct indentation on closing parentheses is especially important as that is how the converter determines the boundary.

	Example that successfully converts:		Example that successfully converts:
Line 25:		Line 25:
	)		)
	</pre>		</pre>

			Something like this is also okay:
			<pre style="color: blue;">
			if %nsl%==On (
			if %PPmode%==Off (
			if %filter%==On (
			set conf=".\emulators\dosbox\Staging_noline_sl.conf"
			goto preinstall)))
			</pre>When all of the closing parenthesis are together, the converter splits them apart and converts each one as appropriate.

	=== Labels must never be placed inside of loops or conditions. ===		=== Labels must never be placed inside of loops or conditions. ===

Main Page

Parricc — Tue, 21 Apr 2026 18:57:08 GMT

Linux Patch

← Older revision		Revision as of 11:57, 21 April 2026
Line 176:		Line 176:
	== Linux Patch ==		== Linux Patch ==
	[[Linux Patch\|Linux Patches]]		[[Linux Patch\|Linux Patches]]

			[[Batch Conversion Limitations]]

	== FAQ ==		== FAQ ==

Batch Conversion Limitations

Parricc — Tue, 21 Apr 2026 18:54:21 GMT

@@ Line 1: / Line 1: @@
-For batch files to successfully convert into bash files for Linux, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.
+For batch files to successfully convert into bash files for Linux and MacOS, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.
-Indentation of nested if statements and loops is necessary.
+=== Indenting nested if statements and for loops is necessary. ===
-Labels must never be placed inside of loops.
+Instead, anything that is nested should have spacing to indicate the level of nesting. The closing parentheses are especially important.

Batch Conversion Limitations

Parricc — Tue, 21 Apr 2026 18:13:55 GMT

describes conversion limitations that must be considered when editing batch files

New page

For batch files to successfully convert into bash files for Linux, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.

Indentation of nested if statements and loops is necessary.

Labels must never be placed inside of loops.

Main Page

Parricc — Tue, 21 Apr 2026 17:53:23 GMT

Renamed Linux Patches Link

← Older revision		Revision as of 10:53, 21 April 2026
Line 175:		Line 175:

	== Linux Patch ==		== Linux Patch ==
	[[Linux Patch\|~~eXoDOS 6.4~~ Linux ~~Patch~~]]		[[Linux Patch\|Linux Patches]]

	== FAQ ==		== FAQ ==

FAQ

Crypt1cMayh3m — Mon, 20 Apr 2026 19:45:14 GMT

Can I merge an eXo project into my existing launchbox install? Can I merge multiple eXo projects into the same LaunchBox install?

← Older revision		Revision as of 12:45, 20 April 2026
Line 42:		Line 42:
	.\Images\<br>		.\Images\<br>
	.\Manuals\<br>		.\Manuals\<br>
			.\Music\<br>
	.\Plugins\<br>		.\Plugins\<br>
			.\Videos\<br>
	.\xml\<br>		.\xml\<br>
	.\~~data~~\Platforms\<br>		.\Data\Platforms\<br>
	.\~~data~~\Playlists\		.\Data\Playlists\
	</blockquote>		</blockquote>
	# <li value="3"> Copy the following file to your target LaunchBox folder from your project folder:		# <li value="3"> Copy the following file to your target LaunchBox folder from your project folder: