| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Simplify primitive interface to read from a socket: now returns just a
single character.
|
|
|
|
|
| |
Now we can just read a single character from the socket, and it isn't
much slower either (maybe 10%).
|
|
|
|
|
|
|
| |
Required fixing an off-by-one error.
(Not bothering writing a test for this since I'm hoping to simplify
$read-from-socket to always return a single character..)
|
| |
|
| |
|
|
|
|
| |
Thanks Ella Couch for reporting this.
|
|
|
|
| |
Fix CI.
|
|
|
|
|
| |
Fix for that annoying popup from the Mac OS firewall: inside tests keep
any opened ports accessible only to localhost.
|
| |
|
| |
|
|
|
|
| |
Thanks Caleb Couch for running into this with $print.
|
| |
|
|
|
|
|
| |
Patch in a new darling from my recent comment at
https://lobste.rs/s/n0d3qo/what_are_you_working_on_this_week/comments/rue8pf#c_rue8pf
|
| |
|
| |
|
|
|
|
| |
Another CI fix.
|
|
|
|
| |
Make sure we clear the socket variable after closing it.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fix CI. 3 different memory leaks in the socket internals.
The hard one was recognizing the need for
`receive-from-client-socket-and-close`.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
More helpful messages when people forget 'load-ingredients'.
|
| |
|
|
|
|
| |
Shorter branches above longer ones.
|
|
|
|
| |
This is just the same as tests for a fake file-system.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This time we're opening real sockets so we might run into issues on
machines with firewalls. Macs for example flash up a dialog warning
people about a port being opened, though it shuts down immediately if
the test passes.
On the flip side, the test has greater verisimilitude. You don't really
need fakes except when you want to pin down the environment a test runs
in. The only way this test might be flaky is on a machine that has lots
of sockets open (so the random port opened by the test is in use for
something else). That and the firewall concern above. Hmm.
|
|
|
|
| |
Its interface now mirrors that of 'read-event'.
|
| |
|
|
|
|
| |
Update syntax highlighting to not color numeric locations like literals.
|
|
|
|
| |
Fix syntax highlighting for labels after commit 3552.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
vim: Stop loading C++-specific syntax highlighting in non-C++ files.
I also figured out why the autocommand wasn't running on the first file:
my local setup for directory-specific vimrc files runs inside an
autocommand, and it runs autocommands recursively inside an autocommand,
and it runs only autocommands inside a 'LocalVimrc' autocommand group to
ensure infinite regress (autocommands running multiple times in
practice). And I'd forgotten this 'feature' of my vimrc setup by the
time I set this up for Mu.
|
|
|
|
|
|
| |
Cleaning up the console interfaces before we start changing the socket
interfaces to look like them. Reading from sockets need to be
non-blocking just like reading from the console.
|
|
|
|
|
| |
Change the interface for reading a URL slightly so that we can directly
use the path in `assume-resources`.
|
| |
|
|
|
|
| |
Fix CI. Revert accidentally-added files.
|
| |
|
| |
|