Jasper St. Pierre da4238ec68 Synchronize shell startup ... The asynchronous nature of extension loading, session loading, and more, makes the code racy as to what is initialized first, and hard to debug. Additionally, since gjs is single-threaded, the only code we're running in a thread anyway is readdir, which is going to be I/O bound, so the code here is actually likely to be faster. Drop this in favor of some good old fashioned synchronous loading.		2013-11-04 11:50:20 -05:00
..
config.js.in	shell: Remove ContactSystem	2012-06-29 11:21:50 +02:00
extensionUtils.js	Synchronize shell startup	2013-11-04 11:50:20 -05:00
fileUtils.js	Synchronize shell startup	2013-11-04 11:50:20 -05:00
gnomeSession.js	Stringify the xml definitions for E4X removal	2013-10-25 08:57:27 +11:00
hash.js	Hash: make .size() constant time	2013-05-12 21:06:34 +02:00
history.js	history: Allow events to bubble up when arrowing past the first/last item	2012-09-18 16:44:08 +02:00
jsParse.js	lookingGlass: Add tab-completion	2011-11-05 13:05:11 -04:00
loginManager.js	Stringify the xml definitions for E4X removal	2013-10-25 08:57:27 +11:00
modemManager.js	Stringify the xml definitions for E4X removal	2013-10-25 08:57:27 +11:00
objectManager.js	Stringify the xml definitions for E4X removal	2013-10-25 08:57:27 +11:00
params.js	*.js: Make emacs modelines consistent	2011-10-11 08:05:12 -04:00
smartcardManager.js	Stringify the xml definitions for E4X removal	2013-10-25 08:57:27 +11:00
util.js	NetworkMenu: make the settings launcher point to the right devices	2013-10-09 18:39:44 +02:00