-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRAFT: reference PR: multi upstreaming #23
Open
qzdl
wants to merge
73
commits into
abcdw:master
Choose a base branch
from
qzdl:master
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
emacs: configure roam emacs: add perfect-margin
- add .PHONY to Makefiles for better UX - add transparency options to sway - add ssh-config options - add emacs-es-mode - add emacs-restclient (-> qzdl) - update channels lock - update emacs-pgtk-pin
TODO generalisation, then mapping of home-shell-type -> vterm-rc zsh -> zshrc cust bash/dash -> subset zsh fish -> fishrc cust TODO copying region with M-w ; yes, vterm-copy-mode, but #musclememorymatters^(TM) - :: https://github.com/akermu/emacs-libvterm#vterm-enable-manipulate-selection-data-by-osc52 vterm uses 'XTerm Control Sequences' - :: https://invisible-island.net/xterm/ctlseqs/ctlseqs.html which I think can be remapped in the shell context, but the challenge remains on the emacs side with respect to the 'mark' etc issue leading vterm-copy-mode's development - :: akermu/emacs-libvterm#75
{C-c C-x i} -> org-id-get-create ~org-id-get-create~ is pretty crucial for the org-roam workflow, so and a free key exists in {C-c C-x i}, which fits semantically with the types of functions in ~org-mode-map : C-c C-x~. {C-c n C-f} -> org-roam-ref-find org-roam-ref-find is super handy to correlate web/cite links with nodes, the ~C-~ layer is free, so it fits well here. {C-c n s} -> rde-search-notes I concede that given the existing keybind conventions this may be better suited as {C-c n M-g}, but my hands know but way to curl; a mod sequence of Ctrl->None->Meta is too much for my brain given the frequency of invocation. this functionality became essential in my habbledashery of a workflow coming from doom; my notes under vc are a 'project' - but I spend most of the time in org, jumping to source, as opposed to the other way around, so it pays to have interactive, incremental search over the corpora, in addition to the current search interfaces at the time of writing: - explicit project ~find-regexp~ {C-x p p PROJ-COMPL RET g} - explicit project ~consult-ripgrep~ {C-x p p PROJ-COMPL RET M-g} - implicit project ~consult-ripgrep~ {M-s M-g} - explicit directory ~consult-ripgrep~ {C-u M-s M-g}
consult-ripgrep I'm a big believer in the power of iterative search - this change lazily adds ~consult-ripgrep~ within the convention of {M-g} used elsewhere (i.e {M-s M-g}) magit-project-status Some custom configuration is applied to project-switch-commands, so it doesn't equal it's initial value, given (get 'project-switch-commands 'standard-value) it seemed appropriate to reinstate the binding explicitly ; note that this action will not cause error or undefined behaviour if the mappings are already defined in ~project-prefix-map~ and/or ~project-switch-commands~. PS: the relevant magit source to preclude project mapping data if modified when loaded -- (defvar magit-bind-magit-project-status t "Whether to bind \"m\" to `magit-project-status' in `project-prefix-map'. If so, then an entry is added to `project-switch-commands' as well. If you want to use another key, then you must set this to nil before loading Magit to prevent \"m\" from being bound.") (with-eval-after-load 'project ;; Only more recent versions of project.el have `project-prefix-map' and ;; `project-switch-commands', though project.el is available in Emacs 25. (when (and magit-bind-magit-project-status (boundp 'project-prefix-map) ;; Only modify if it hasn't already been modified. (equal project-switch-commands (eval (car (get 'project-switch-commands 'standard-value)) t))) (define-key project-prefix-map "m" #'magit-project-status) (add-to-list 'project-switch-commands '(magit-project-status "Magit") t))) --
* rde/examples/abcdw * configs.scm - add new packages: consult-eglot, consult-recoll - add remaining non-feature, pre-rde emacs packages * emacs.org, emacs.scm - add ob-async - add rde-sanity load command - fix bindings H-s-hjkl - fix bindings H-s-M-hjkl - fix bindings H-s-\ * stale/guix-related/guix/channels-lock - update pins
a useful file at the root sanity.scm -- (use-modules (rde packages) (rde examples abcdw configs)) -- emacs -- (defun rde-sanity (async-shell-command "cd $HOME/git/sys/rde && guix repl -L . sanity.scm")) --
rde-project-vterm this is really just a rip from `project-shell' -- happily, vterm respects `default directory'.
- magit start collapsed - work agenda - org-link ; man ; ol-man - org-log-done 'time - ingest files to include prefix-arg helper - aws & kubectl ui
also, fixing clock-files <-> files-clock
also, patched modus to test Prot's ement theming rde: packages: emacs-modus-themes: add ement patch
including a new package, tessen@1.3.1
- adds config package - emacs-justify-kp
note: this will be valid for any theme string parsed by rofi, which is any named theme file implicitly located in the theme search path, but more usefully, can be some arbitrary file which can be enclosed with `local-file'. example usage: (feature-rofi #:theme (local-file "config/rofi/themes/base16-default-dark.rasi"))
used for providing additional options directly to sway, such as for the use of nonstandard DRM devices: (feature-sway-run-on-tty #:launch-args "--unsupported-gpu --debug &>/tmp/sway")
the `which-key' indirect buffer starts as 'fundamental-mode, thus global-olivetti-mode will still apply, giving a squashed unreadable key-suggestion buffer. - note: we can instead check `which-key-buffer-name', or just use the hardcoded string - note: updates to `global-olivetti-ignore-[modes|buffer]' variables may require fresh enabling of `global-olivetti-mode', if they are inlined during compilation related might be the use of 'olivetti-mode' in the minibuffer, which is useful in my 5120x1440 monitor, lest I look 45 centimeters from the center of my screen each time I pop the minibuffer. It's quite cool as the bindings to expand the buffer `C-c }' still work here. I have used this as: (add-hook 'minibuffer-mode-hook 'olivetti-mode) or some variant for better width: (add-hook 'minibuffer-mode-hook (lambda () (let ((olivetti-body-width 200)) (olivetti-mode))))
rde: packages: Add wlroots patch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
not to merge, reference on #tropin