Grep for space indentation (#54850)

#54604 atomizing
Since a lot of the space indents are in lists ill atomize those later

code/modules/modular_computers/file_system/programs/radar.dm

@@ -74,13 +74,13 @@
 			scan()
 
 /**
-  *Updates tracking information of the selected target.
-  *
-  *The track() proc updates the entire set of information about the location
-  *of the target, including whether the Ntos window should use a pinpointer
-  *crosshair over the up/down arrows, or none in favor of a rotating arrow
-  *for far away targets. This information is returned in the form of a list.
-  *
+ *Updates tracking information of the selected target.
+ *
+ *The track() proc updates the entire set of information about the location
+ *of the target, including whether the Ntos window should use a pinpointer
+ *crosshair over the up/down arrows, or none in favor of a rotating arrow
+ *for far away targets. This information is returned in the form of a list.
+ *
 */
 /datum/computer_file/program/radar/proc/track()
 	var/atom/movable/signal = find_atom()
@@ -116,13 +116,13 @@
 	return trackinfo
 
 /**
-  *
-  *Checks the trackability of the selected target.
-  *
-  *If the target is on the computer's Z level, or both are on station Z
-  *levels, and the target isn't untrackable, return TRUE.
-  *Arguments:
-  **arg1 is the atom being evaluated.
+ *
+ *Checks the trackability of the selected target.
+ *
+ *If the target is on the computer's Z level, or both are on station Z
+ *levels, and the target isn't untrackable, return TRUE.
+ *Arguments:
+ **arg1 is the atom being evaluated.
 */
 /datum/computer_file/program/radar/proc/trackable(atom/movable/signal)
 	if(!signal || !computer)
@@ -134,30 +134,30 @@
 	return (there.z == here.z) || (is_station_level(here.z) && is_station_level(there.z))
 
 /**
-  *
-  *Runs a scan of all the trackable atoms.
-  *
-  *Checks each entry in the GLOB of the specific trackable atoms against
-  *the track() proc, and fill the objects list with lists containing the
-  *atoms' names and REFs. The objects list is handed to the tgui screen
-  *for displaying to, and being selected by, the user. A two second
-  *sleep is used to delay the scan, both for thematical reasons as well
-  *as to limit the load players may place on the server using these
-  *somewhat costly loops.
+ *
+ *Runs a scan of all the trackable atoms.
+ *
+ *Checks each entry in the GLOB of the specific trackable atoms against
+ *the track() proc, and fill the objects list with lists containing the
+ *atoms' names and REFs. The objects list is handed to the tgui screen
+ *for displaying to, and being selected by, the user. A two second
+ *sleep is used to delay the scan, both for thematical reasons as well
+ *as to limit the load players may place on the server using these
+ *somewhat costly loops.
 */
 /datum/computer_file/program/radar/proc/scan()
 	return
 
 /**
-  *
-  *Finds the atom in the appropriate list that the `selected` var indicates
-  *
-  *The `selected` var holds a REF, which is a string. A mob REF may be
-  *something like "mob_209". In order to find the actual atom, we need
-  *to search the appropriate list for the REF string. This is dependant
-  *on the program (Lifeline uses GLOB.human_list, while Fission360 uses
-  *GLOB.poi_list), but the result will be the same; evaluate the string and
-  *return an atom reference.
+ *
+ *Finds the atom in the appropriate list that the `selected` var indicates
+ *
+ *The `selected` var holds a REF, which is a string. A mob REF may be
+ *something like "mob_209". In order to find the actual atom, we need
+ *to search the appropriate list for the REF string. This is dependant
+ *on the program (Lifeline uses GLOB.human_list, while Fission360 uses
+ *GLOB.poi_list), but the result will be the same; evaluate the string and
+ *return an atom reference.
 */
 /datum/computer_file/program/radar/proc/find_atom()
 	return