my emacs is completely fucked
Post
Replies:
15
This parameter was introduced in Emacs version 25.1 to support
applications that use large margins to center buffer text within a
window and should be used, with due care, exclusively by those
applications. It might be replaced by an improved solution in
future versions of Emacs.
most people don't make perfect decisions the first time! that's why we iterate!
turns out my emacs problems were as usual the result of absurd and truly unnecessary macro trickery
regex matching as a language feature tied with the logic you perform around regex matching is still a rly cool idea though........hoping to make it work for my vaporware shell language
props to stefan monnier and the very sweet people on emacs-devel for demonstrating a powerful and extensible type system within a tiny little language. pcase is sooooooo cool. singlehandedly convinced me that there is a world of type safety beyond what languages like rust can provide
there's a rly cute "regex contract" that they're doing in the stdlib so your regex to match bugs and issue links magically become clickable URLs https://codeberg.org/cosmicexplorer/emacs/src/commit/125b3588c9a69625aa72cb3a86c332a804d02458/lisp/progmodes/bug-reference.el#L130-L155
it's really really good work, but i am reasonably certain it's overly stringent and erroring as a result of my explicitly-numbered groups (which is critical for making regexps even remotely composable)
cannot overstate how slick it is that emacs lets you magically turn text into clicky buttons. that shit is crazy
maybe if i'm actually right on this here i could have my first commit more than a single parenthesis in emacs. that would be neat
anyway did you know emacs just gives you a (load-average) function now? it's v interesting to compare it to python and java bc emacs is vv long-running like #enterprise servers but it obviously only has eight megabytes to swap around. we make do
the regex contract is SUCH a good idea though i wish i'd had it
i'm absolutely gonna propose a slight change to the ordering of this alist of known forges though lol https://codeberg.org/cosmicexplorer/emacs/src/commit/125b3588c9a69625aa72cb3a86c332a804d02458/lisp/progmodes/bug-reference.el#L244-L250
codeberg at number THREE????
i am an incredible goalie i could play for the codeberg football team
oh my god i found the file paths and directory traversal part of the info pages and saw the link to the TRAMP docs. michael albinus is so cool and nice to me
python pathlib and emacs stay winning
On MS-DOS and MS-Windows, these functions (like the function that
actually operate on files) accept MS-DOS or MS-Windows file-name syntax,
where backslashes separate the components, as well as POSIX syntax; but
they always return POSIX syntax. This enables Lisp programs to specify
file names in POSIX syntax and work properly on all systems without
change.(1)
i have a really good model of posix paths in rust which brings type safety to the filesystem layer in case anyone wants that sort of thing. but i need a windows collaborator before proposing as a rust RFC bc i can't test it myself. especially fuzzing the conversions between platform models
i have some really exciting work with filesystems that actually does syscalls but there is an abstraction for directory traversal which i don't think has a direct analog on windows. maybe cpython would be interested though
