Skip to content
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

Migrated random local quick TODO entries... #6

Open
3 of 12 tasks
xparq opened this issue Aug 25, 2023 · 0 comments
Open
3 of 12 tasks

Migrated random local quick TODO entries... #6

xparq opened this issue Aug 25, 2023 · 0 comments

Comments

@xparq
Copy link
Owner

xparq commented Aug 25, 2023

  • Ctrl + Del/Backsp -> sz/delete-to-next-word-boundary, sz/backspace-to-prev-word-boundary

  • Proper file (buffer) switching (FWIF: M1/M3 on buffer name is prev/next)

  • Divide the init/cfg into a "free" sanitization baseline layer, plus extras. -> Reorg. config/init so that a clean, "universal" baseline is easier to define #11!
    Kinda done, but not double-checked how free the baseline is.

  • conemacs: load much less crap on startup, but still keep the sane defaults! (Requires the one above.)

  • Custom custom.el: is it actually used?!
    Yes, but not sure if I still need to load it manually...
    -> Some package manipulations updated it, but also OVERWROTE EVERYTHINT ELSE THERE! :-o

  • CompAny: also allow dismissing offered completions by delete, not just backspace

  • Proper scrolling to botton on Ctrl-End

  • Speedbar etc.: no line numbers there...

  • Speedbar: why does it only show certain files (like not this TODO or the README,
    not even when loaded)?!

  • Speedbar: don't open randomly in other windows (panes) after closing it sidebar!

  • Migrate away from the libs/packs installed via Debian into /usr/share/* and
    /etc and who knows where, and put everything into a unified .emacs.d tree,
    installed via emacs itself.

    One motivation was that the Debian install tree is full of symlinks,
    which don't work on Windows (NTFS + WSL + W10 interop issue), so that
    tree can't be shared: everything would need to be installed on Windows
    via Emacs anyay -- so, if that local tree is cross-platform, it should
    be used on Linux, too!

    • Understand what can and cannot be installed in this uniform way both on
      Linux and Windows
    • with the occasional checks/switches/branches across the two
      • E.g. just copying package-installed stuff from one to the other seems fine!
  • See how others group their configs: do they go thematically, e.g. putting
    the key bindings along with all the other cfg aspects of a given package
    or feature, or do they tend to keep the keys separate?

xparq added a commit that referenced this issue Aug 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant