Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This function lets me interactively apply a patch from the currently
opened notmuch message to the depot.
|
|
|
|
|
|
Cheddar now needs to be passed the --about-filter flag to toggle the
behaviour for rendering Markdown into HTML.
By default Markdown will be highlighted like normal source code (i.e.
cgit source-filtering is the default behaviour).
|
|
|
|
This advice is potentially defined before the autoloads for telega
have run, which means that the macro-expansion fails and
`telega-ins-fmt` is looked up as a function.
With this setup the initialisation works as expected.
|
|
Lets evaluate this for a bit. With the current settings it even seems
to render _okay_ on nugget.
|
|
|
|
The lambda that acts as the sentinel for building SBCL with packages
needs to be able to capture variables if lexical binding is enabled,
which is made possible by the lexical-let form.
|
|
Not configuring this automatically yet, I mostly want to try it out.
|
|
|
|
Adds a function that can launch Sly with a pre-configured SBCL for a
Lisp derivation in the depot.
This makes it convenient to spin up development environments for Lisp
libraries and programs by simply calling `M-x nix/sly-from-depot RET
tools.something`.
This relies on `nix-depot-path` being configured currently as I have
not yet reliably added the depot to my NIX_PATH on all machines.
|
|
Sets up Lisp modes in Sly REPL and points at the local hyperspec
checkout.
In fact the Hyperspec bit should probably be managed by Nix, but one
step at a time.
|
|
|
|
|
|
|
|
See explanatory comment.
|
|
|
|
Sounds good, doesn't work.
(Okay, it does - but not like I want it to and with too many caveats
at the moment - maybe later)
|
|
This is required because the configuration is used on machines where
fish comes from Nix, and on ones where it does not.
|
|
The signature itself is read from ~/.signature
|
|
|
|
This code has moved into a patch for notmuch itself.
|
|
|
|
|
|
Advises notmuch to display `Date` headers using dottime.
|
|
This gives users from Elisp slightly more flexibility about the
display of dottime.
|
|
|
|
No longer required because Gmail does this automatically.
|
|
Fetching credentials is no longer handled by msmtp itself.
|
|
|
|
|
|
Advising these functions apparently breaks things internally.
|
|
Instead of splitting below and moving the target buffer into the new
split, split and move the buffer into the active window.
The other way around does (for some reason I don't fully understand)
not work because `split-window-below` may return invalid windows.
|
|
|
|
Configures edwina using `s-w` as the key prefix (in line with my other
EXWM-related commands).
An additional function is added that switches to a buffer (borrowing
the implementation from `ivy-switch-buffer`) but splitting it into a
new window instead.
|
|
|
|
|
|
No configuration for this yet, I just want to try it out. It seems
like an interesting way of managing Emacs windows!
|
|
Uses GitHub-like styling for <pre> elements, i.e. slight padding and
background colour highlighting.
|
|
Implements fully static (i.e. no JavaScript!) highlighting of code
blocks when rendering Markdown.
This works by walking through the Comrak AST and replacing any code
blocks with pre-rendered HTML blocks.
Syntaxes are chosen based on the "block info", which is the string
users put after the block's opening fence. This can either be
a (case-insensitive) name of a syntax, or alternatively a file
extension associated with the desired syntax.
The theme is set to one that imitates GitHub.
|
|
|
|
Renders any ".md" file by pushing it through the Comrak rendering
pipeline.
This does not yet implement syntax highlighting of fenced blocks, but
we're getting there.
|
|
Generalises the two bits of the program that will be required either
way (extension parsing and syntax loading).
A dependency on Comrak is introduced as I think GitHub-flavoured
Markdown (with all its fancy extensions) is desirable!
|
|
This uses Nix to inject the path to the syntax highlighting assets
that ship with the bat source code into the cheddar build at compile
time, where the Rust compiler then inserts it into the binary via
macros.
bat has a lot of custom syntax highlighting definitions that they
collected from all over the place (including for languages like Nix!)
and this makes them accessible to cheddar.
Also if you're reading this, can you just take a moment to appreciate
how incredible it is that Nix just lets us do something like this?!
|
|
The first step with this tool will be to use it as a source-filter for
cgit. The second step is to use it as the Markdown renderer by
depending on one of the Markdown libraries, with integration for
rendering code snippets directly.
|
|
This moves the various projects from "type-based" folders (such as
"services" or "tools") into more appropriate semantic folders (such as
"nix", "ops" or "web").
Deprecated projects (nixcon-demo & gotest) which only existed for
testing/demonstration purposes have been removed.
(Note: *all* builds are broken with this commit)
|
|
|