profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/duckwork/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Case Duckworth duckwork Baton Rouge, LA https://www.acdw.net Case Duckworth is a LIBRARIAN living in Baton Rouge who uses Linux and codes sometimes, badly.

duckwork/bin 2

The bin I put little scripts in

duckwork/electric-cursor 2

#emacs minor-mode to automatically change the cursor

duckwork/autocento 1

Website for Autocento experiment (thesis)

duckwork/cribbed 1

AwesomeWM modules, widgets, etc.

duckwork/dmenu-overkill 1

dmenu-overkill: way too much for a simple menu

duckwork/.emacs.d 0

mirror of https://git.sr.ht/~acdw/.emacs.d

duckwork/2bwm 0

A fast floating WM written over the XCB library and derived from mcwm.

duckwork/awesome-ezconfig 0

Easier key and button setup for awesome wm

duckwork/awesome-remember-geometry 0

Remember client location when switching between floating, tiling and maximized

duckwork/awesomewm-net 0

Network widgets for Awesome WM

starteddickmao/commercial-emacs

started time in 2 days

starteddanielfm/smudge

started time in 4 days

issue openedemacs-circe/circe

Confusing logic for `circe-server-killed-confirmation` settings

Hi there, and thanks for circe!

I'm writing an issue instead of submitting a PR because I want to make sure I'm not misunderstanding behavior here. According to the docstring of circe-server-killed-confirmation, a value of kill-all should kill all associated channel buffers without prompting the user. However, the code for circe-server-killed asks the user to confirm whenever circe-server-killed-confirmation is non-nil, including when it's kill-all.

However, when circe-server-killed-confirmation is nil, only the server buffer is killed. The way the options read, I thought nil would only kill the server buffer, kill-all would kill the server buffer and associated buffers without confirmation, and ask-and-kill-all would kill the server buffer and associated buffers with confirmation.

Have I misunderstood the logic of these choices, or is this a bug in circe-server-killed? From what I can tell, at this moment kill-all and ask-and-kill-all are identical except in the question they ask the user, which doesn't really make any sense.

Anyway, just let me know. I'm happy to submit a PR if it's a bug.

created time in 5 days

startedalezost/org-ref-prettify.el

started time in 5 days

PR opened d12frosted/flyspell-correct

Add `defgroup' for customization options

defgroup enables the Custom buffer to link to its parent group, which I made flyspell here. Though now that I'm looking at the other variables in this file, I'm not sure what the thinking is behind some options/modes being under flyspell and some being under flyspell-correct.

+5 -0

0 comment

1 changed file

pr created time in 6 days

push eventduckwork/flyspell-correct

Case Duckworth

commit sha 700be27df3308cee5b5b0b99306ebc95830aa795

Add `defgroup' for customization options `defgroup` enables the Custom buffer to link to its parent group, which I made `flyspell` here. Though now that I'm looking at the other variables in this file, I'm not sure what the thinking is behind some options/modes being under `flyspell` and some being under `flyspell-correct`.

view details

push time in 6 days

fork duckwork/flyspell-correct

Distraction-free words correction with flyspell via selected interface.

fork in 6 days

startedodeke-em/drive

started time in 9 days

startedgRastello/ytel

started time in 9 days

startedalphapapa/makem.sh

started time in 10 days

issue closedalphapapa/unpackaged.el

Possible to make `sort-sexps` take a sorting function?

My lisp-fu is not so advanced to do this, but I'd love ot pass something like, (sort-sexps beg end &optional accessor) to sort specifically on a certain element of a list (i.e., sort all defines by cadr).

Looks like the collect (cons (buffer-substring...) code needs to be modified, but I'm not sure how to define a searcher for a certain element of each read list and return its begin and end points in the buffer.

closed time in 12 days

duckwork

issue commentalphapapa/unpackaged.el

Possible to make `sort-sexps` take a sorting function?

Oh, right, haha :) ACDW was taken already on Github!

duckwork

comment created time in 12 days

issue commentakermu/emacs-libvterm

Feature request: Act as Eshell's visual term

FYI this package I found does exactly this (approach [a]).

tomfitzhenry

comment created time in 13 days

issue commentalphapapa/unpackaged.el

Possible to make `sort-sexps` take a sorting function?

It does indeed. I've written my own function (viewable in all its awfulness here) that sorts my init file by setup forms. Exactly what I was looking for, thanks!

duckwork

comment created time in 13 days

startedtrev-dev/emacs

started time in 13 days

startedmmarshall540/repeaters

started time in 15 days

issue commentalphapapa/unpackaged.el

Possible to make `sort-sexps` take a sorting function?

Oh, that'll work! Thanks :)

I could use an &optional argument for key, right, instead of a cl-defun ? Just making sure.

duckwork

comment created time in 15 days

startedamno1/emacs-term-toggle

started time in 15 days

PR opened dieggsy/esh-autosuggest

Autoload `esh-autosuggest-mode`

Otherwise I need to either (require 'esh-autosuggest) or (autoload 'esh-autosuggest-mode "esh-autosuggest") in my config.

+1 -0

0 comment

1 changed file

pr created time in 16 days

push eventduckwork/esh-autosuggest

Case Duckworth

commit sha 9261d3c8ff92cdd0cb35fc0fa79054f1b650c8ad

Autoload `esh-autosuggest-mode` Otherwise I need to either `(require 'esh-autosuggest)` or `(autoload 'esh-autosuggest-mode "esh-autosuggest")` in my config.

view details

push time in 16 days

fork duckwork/esh-autosuggest

Fish-like autosuggestions in eshell.

fork in 16 days

startedphikal/setup.el

started time in 16 days

PR opened phikal/setup.el

Fix quoting bug in `:file-match`

:file-match forms were throwing void-variable errors. Adding a quote mark fixes it.

+1 -1

0 comment

1 changed file

pr created time in 16 days

push eventduckwork/setup.el

Case Duckworth

commit sha 3a6edb5c8d3f418628834044328ae51bccde200c

Fix quoting bug in `:file-match` `:file-match` forms were throwing `void-variable` errors. Adding a quote mark fixes it.

view details

push time in 16 days

fork duckwork/setup.el

(mirror) Helpful configuration macro

https://git.sr.ht/~pkal/setup

fork in 16 days

issue openedalphapapa/unpackaged.el

Possible to make `sort-sexps` take a sorting function?

My lisp-fu is not so advanced to do this, but I'd love ot pass something like, (sort-sexps beg end &optional accessor) to sort specifically on a certain element of a list (i.e., sort all defines by cadr).

Looks like the collect (cons (buffer-substring...) and code needs to be modified, but I'm not sure how to define a searcher for a certain element of each read list and return its begin and end points in the buffer.

created time in 16 days

issue openedjdenen/mastodon.el

Command to open URLs of toots?

Sometimes, say in IRC, someone will post a link to a toot or series of toots. Is it possible to have a command in this package to hook into browse-url or similar, so we can open toots in Emacs from a URL?

created time in 17 days

startedstardiviner/sdcv.el

started time in 19 days

starteddsedivec/dot-emacs-d

started time in 19 days

startedLaurenceWarne/libro-finito

started time in 19 days