my emacs is completely fucked
Post
Replies:
15
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
The operating system groups files into directories. To specify a file,
you must specify the directory and the file's name within that
directory.
cannot express how delighted reading this sort of documentation makes me. not just "here's an API" but "here's why there's a whole section on this topic and we have some functions for parts of it"
maybe that excerpt sounds really overly basic but this is exactly the level you have to be thinking at to have a path abstraction that works robustly across platforms
the docs just called me out for my use of the term "path" right as i said that above!!!! bc the stuff emacs works on is largely concrete files as opposed to search paths (and in fact i totally agree with their distinction here)
this distinction is actually like the most interesting part of my directory traversal work: using file descriptors and inodes to confidently read and write and have a clear concept of progress and completion, instead of path strings which are fundamentally racy and cannot be deduplicated
@hipsterelectron so wait what is different in practice when you do that
