Florian Müllner f250643385 style: Use space after catch ... We are currently inconsistent with whether or not to put a space after catch clauses. While the predominant style is to omit it, that's inconsistent with the style we use for any other statement. There's not really a good reason to stick with it, so switch to the style gjs/eslint default to. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/607		2019-07-01 23:44:11 +02:00
..
config.js.in
extensionUtils.js	style: Use space after catch	2019-07-01 23:44:11 +02:00
fileUtils.js	cleanup: Remove unused variables	2019-07-01 23:44:10 +02:00
gnomeSession.js
history.js
ibusManager.js	style: Use space after catch	2019-07-01 23:44:11 +02:00
inputMethod.js	inputMethod: Handle OSK hiding after unfocus	2019-03-04 18:24:38 +00:00
introspect.js	introspect: Include sandboxed-app-id as well	2019-05-16 13:02:08 +00:00
jsParse.js	cleanup: Remove unneeded escapes in regex	2019-07-01 23:44:10 +02:00
keyboardManager.js	cleanup: Use Array.includes() to check for element existence	2019-07-01 21:28:52 +00:00
loginManager.js	style: Use space after catch	2019-07-01 23:44:11 +02:00
meson.build
modemManager.js	modemManager: improve check for CDMA system identifier	2019-05-27 08:36:05 -07:00
objectManager.js	style: Use space after catch	2019-07-01 23:44:11 +02:00
params.js
permissionStore.js
smartcardManager.js
systemActions.js	systemActions: Only do prefix matches	2019-05-15 17:20:21 +00:00
util.js	style: Use space after catch	2019-07-01 23:44:11 +02:00
weather.js	style: Use space after catch	2019-07-01 23:44:11 +02:00