/scripts/

wn-heading-color.css'/>
aboutsummaryrefslogtreecommitdiff
path: root/.dir-locals.el
AgeCommit message (Expand)Author
2024-11-29.dir-locals.el: Configure indentation for home-environment....* .dir-locals.el (scheme-mode): Indent home-environment same as operating-system. Change-Id: Ie2cfa58f02d081c1e331c7d30beb77f0868f5cdd Signed-off-by: Ludovic Courtès <ludo@gnu.org> Tomas Volf
2024-09-21.dir-locals.el: Add tempel snippets....Change-Id: Ic16f571f26fffee12e478e00c54be55e6eb90831 Signed-off-by: jgart <jgart@dismail.de> Nicolas Graves
2024-05-13store: Add with-store/non-blocking....For some applications, it's important to establish a non-blocking connection rather than just making the socket non-blocking after the connection is established. This is because there is I/O on the socket that will block during the handshake. I've noticed this blocking during the handshake causing issues in the build coordinator for example. This commit adds a new with-store variant to avoid changing the behaviour of with-store/open-connection to ensure that this change can't break anything that depends on the blocking nature of the socket. * guix/store.scm (open-unix-domain-socket, open-inet-socket): Take #:non-blocking? and use SOCK_NONBLOCK when calling socket if appropriate. (connect-to-daemon, open-connection, call-with-store): Take #:non-blocking? and pass it on. (with-store/non-blocking): New syntax rule. * .dir-locals.el (scheme-mode): Add entry for with-store/non-blocking. Change-Id: I8225762b78448bc1f7b698c8de5d736e13f577bf Christopher Baines
2024-05-13.dir-locals: Configure indentation for swap-space....* .dir-locals.el (scheme-mode): Indent swap-space same as file-system. Change-Id: Id9f2cbd3c81343b479ab1e4df29c65f8b5bd739f Signed-off-by: Ludovic Courtès <ludo@gnu.org> Tomas Volf
2024-04-03store: database: Remove with-statement and associated code....I think using dynamic-wind to finalize all statements is the wrong approach. Firstly it would be good to allow reseting statements rather than finalizing them. Then for the problem of handling errors, the approach I've settled on in the build coordinator is to close the database connection, since that'll trigger guile-sqlite3 to finalize all the cached statements. This reverts commit 5d6e2255286e591def122ec2f4a3cbda497fea21. * .dir-locals.el (scheme-mode): Remove with-statement. * guix/store/database.scm (call-with-statement): Remove procedure. (with-statement): Remove syntax rule. (call-with-transaction, last-insert-row-id, path-id, update-or-insert, add-references): Don't use with-statement. Change-Id: I2fd976b3f12ec8105cc56350933a953cf53647e8 Christopher Baines
2024-04-03store: database: Remove call-with-savepoint and associated code....While care does need to be taken with making updates or inserts to the ValidPaths table, I think that trying to ensure this within update-or-insert is the wrong approach. Instead, when working with the store database, only one connection should be used to make changes to the database and those changes should happen in transactions that ideally begin immediately. This reverts commit 37545de4a3bf59611c184b31506fe9a16abe4c8b. * .dir-locals.el (scheme-mode): Remove entries for call-with-savepoint and call-with-retrying-savepoint. * guix/store/database.scm (call-with-savepoint, call-with-retrying-savepoint): Remove procedures. (update-or-insert): Remove use of call-with-savepoint. Change-Id: I2f986e8623d8235a90c40d5f219c1292c1ab157b Christopher Baines