Age | Commit message (Collapse) | Author | Files | Lines |
|
This is handy!
|
|
Instruct Tramp to use my SSH settings in .ssh/config.
|
|
Generate KBDs to call `find-file` on the bookmark.
|
|
My google-briefcase has subsumed this responsibility.
|
|
My custom language settings conflict with Google-Emacs's language settings, and
I'm not interested in finding a more harmonious solution. For now, I'm dropping
my settings altogether in favor of Google-Emacs's settings.
|
|
Add fzf to PATH.
|
|
I'd rather be able to jump straight here instead of visiting a file or directory
first.
|
|
On my work machines, I'm finding home-manager to be more bothersome than
helpful. I'm preferring a simpler workflow for the time being.
|
|
The code in `wpc-nix.el` relies on `nix-env` being available on $PATH.
|
|
After ~1-2 hours of debugging, I realized that locally I was reading from .envrc
but when Emacs initializes, it is not reading from .envrc. I don't know how to
ideally handle this, so for now I'm including GOOGLE_BRIEFCASE as an environment
variable and moving on with my life.
|
|
I've reconsidered; setting this to just '(cl-functions) is not what I want.
|
|
Trying to be more idiomatic.
|
|
Consider moving some of this logic into my work-specific configuration.
|
|
I was previously relying on the variable `server-process` being set, but this
only resulted in false-negatives and broken initializations. This should make my
Emacs initialization more stable.
|
|
direnv.el needs direnv available on $PATH.
|
|
When the `window-system` is set, use `solarized-light`. When it's not,
use `wombat`.
|
|
Only attempt to start the Emacs server if there isn't already one
running.
|
|
Only when `window-system` is set.
|
|
I would like to restore these KBDs.
|
|
See the URL I linked to for more information.
|
|
I'm defining a fork of this function in my work configuration, so I longer want
this here.
|
|
As the name suggests, `f-parent-of?` only returns true when A is a *parent* of
B. What I want instead if `f-ancestor-of?`.
|
|
I need this for Nix code that exists outside of this repository.
|
|
See the explanatory comment that I left in the code.
|
|
In the past I used `defconst` in many of my Elisp libraries where I should've
used something like:
```elisp
;; some/path/to/some-lib.el
(defgroup some-lib nil)
(defcustom some-lib-setting nil
:group 'some-lib)
```
When I encounter code that I should've structured this way, I'm cleaning it up
to prefer this more idiomatic pattern.
|
|
While attempting to debug why pressing `C-s-s` from an X-window screenshots my
entire screen, I switched from `call-process` to `make-process`, which is
async.
I still haven't debugged the original issue, but I think this is an improvement
regardless.
|
|
When I removed the KBD logic from fonts.el, I should have moved it here, but I
did not.
|
|
Looks like when I linted my Emacs I forgot to change the prefix from
`pulse-audio/` to `pulse-audio-`.
|
|
Now that Emacs is capable a rendering font ligatures, I defined a function to
enable them in fonts.el. Everything works, and it's beautiful.
|
|
Now that my `script.el` is behaving as expected (wahoo!), start linting away
anything that shows up in the `*Warnings*` and `*Errors*` buffers.
|
|
TL;DR:
- Prefer cl-lib
- Prefer spaces to tabs
- Resolve various checkdoc complaints
|
|
I originally liked this pattern, but now I'd prefer to put everything in
keybindings.el.
|
|
Since I'm calling `(require 'general)` in `wpc-package.el`, which gets called at
the beginning of my `init.el` file, all sub-modules have `general`. I originally
wanted this, but I'm beginning to rethink that preference.
After `script.el` broke my CI because of a missing `general` dependency, I'm
fixing it for `buffer.el` and all other modules that consume `general`.
|
|
Since script.el depends on buffer.el now, buffer.el fails to evaluate because of
a missing dependency on ts.el.
Blindspots like this make me want to eventually support testing individual loads
of each of the libraries in my .emacs.d/wpc directory.
|
|
`use-package` complains that `add-hook-before-save` doesn't exist. This is
because it's now named `macros-add-hook-before-save`.
This fixes that.
|
|
Problem: `(bufferp "*Warnings*")` always returns `nil` because it expects a
buffer object. Thankfully I wrote a function called `buffer-exists?`, which is a
more DWIM alternative of `bufferp`.
Hopefully now CI should fail!
|
|
TL;DR:
- Require cl-macs.el for modules using CL-style macros like `cl-defun`
- Require struct.el for call to `struct-set!`
|
|
I haven't used Slack in awhile -- let alone Slack from Emacs.
|
|
TL;DR:
- Assert that the path to the init.el exists
- Check *Errors* buffer in case an error is uncaught but logged
- Log a message when Emacs successfully initializes
|
|
TL;DR:
- Remove `require` statements from init.el
- Remove unused, auto-install KBDs for bookmark.el
- Remove unused `require` statements from clipboard
- Remove unused, commented-out code
I would like for an Elisp linting stage to test for unused `require` statements,
but I'm unsure how practical that is to support.
|
|
maybe.el -> prelude.el -> maybe.el
I should test for circular-dependencies in CI...
|
|
Here's what happened:
My `emacs.glinux` derivation relies on gLinux `/usr/bin/emacs`, and Google
recently published version 27, so all corporate machines (i.e. this laptop)
switched from Emacs 26 to Emacs 27 overnight.
However, my Nix derivation was building all of the packages for Emacs 26, so
some packages were compatible while others weren't.
The Elisp package, `emr`, doesn't build for version 27, so I dropped it
altogether.
|
|
After switching my namespace separator from "/" to "-" the function,
`alist-get`, clashed (surprise!) with the pre-existing function, `alist-get`. As
I was struggling to debug my broken Emacs (it broke bc Emacs 27 rolled out), and
I changed the module name, "alist", to "al" attempting to defuse the issue.
|
|
Sorry, @grfn! I haven't used Clubhouse is awhile...
|
|
No reason for init-emacs to block lint-elisp.
|
|
While I don't agree with what checkdoc is advising here, I'd rather not fight
it.
|
|
I created a strangely named Elisp module, >.el, just to appease the CI gods. My
gut tells me that this is a desperate idea and fails the smell test. I'm pretty
eager to pass the linting phase of my Elisp CI, however, and I can always revert
this.
|
|
In order for this to scale, I need to solve two things:
1. Ad-hoc ignore fill-column rules for URLs and other exceptions.
2. Run Elisp flychecker without evaluating my Elisp code and firing its
side-effects.
|
|
Consuming my newly defined Nix utilities.
|
|
I haven't used this since I wrote it months ago...
|