?
line modes
+monospace
*bold
_italic
)right justify
=centered text
>quote
~sampel-palnet
!https://..image.jpg
<http://link.com
the first character of a line sets its mode.
a mode applies to the whole line.
[view hawk code]
[hawk] consists of that
[userspace] software which admits of
[ubiquitous html5 clients].
- urbit precepts on “real software”
i'm considering pausing 499 work
for a week or so
and just implementing
a simple build cache in 500.
because it turns out these little
manx apps are pretty ergonomic to
write. the only issues are:
- the speed
- the unimplemented features (like fine-grained access control)
both are solvable without 499
---
have been meaning to write up
a post fully explaining my
thoughts on software distribution.
the tldr is:
most apps fit in a single file
if your programming environment
is doing what it should.
once this is true, the optimal
installation experience is to
simply paste the code into the
place where you want to install
the apps.
this gives you a relationship with
the code. if you ever want to change
it, you know where it is.
quality software with a focus
on simplicity, clarity,
and frugality.
- the suckless.org philosophy page
still working on the frugality...
there's a need for speed.
I still think that there needs to be an idiot-proof (idiots can't copy paste) version of software distribution. (Read: it needs a button)
hawk is just a worse version of
traditional software until the
user understands that the code in
the code tab controls the display
of the page.
so this code:
[%'~' rest=*]
::
=/ mention (slaw %p line)
?~ mention ;div:(-p)
;div.mono.o8.bold
=data-mention +:(scow %p u.mention)
;- (scow %p u.mention)
==
...just turns it bold currently? but also labels it as a "mention" in such a way that may be used for more (such as link to their hawk page or send them a notification) at some later time?
whoops, here
... but will, you also have a small whoops in your instructions, which led to my whoops.
bold is done with *bold
monospace is done with +monospace
no thank you for making this!
persistent reading position is interesting, as re-loading causes it to gradually scroll down.
what was at the bottom becomes what's at the top (roughly).
took me a few reloads to figure out what it was doing.
actually, on further testing, it goes down, down, down until ~sarlev's "I still think that there needs to be an idiot-proof" post.
then it stays there, stationary, on all subsequent reloads.
presumably that is related to him always being right.
perhaps the software is interpreting that as "he should get the last word".
that would make sense.
~ripwyd_dolseg, eh?
a long-lost cousin?
it is fascinating that each message gets it's own @p!
the above e.g. is #ranmeg-binlug
ok, further troubleshooting (can't help myself?):
I zoomed in the browser magnification to 150% and determined it does not, in fact, respect
~sarlev
properly. at 150% it stops moving after seven reloads.
other magnifications are different.
actually at 100% it seems to continue all the way to the end. so i must have had it zoomed in previously.
the persistent reading position just means:
when you reload,
(or come back to the page after having closed it)
you should end up near the thing you were previously
looking at.
this means if you scroll to the bottom each time
you read the forum, when you get to the bottom,
you know you've read everything that's new.
can confirm it is repaired.
amazing turn-around time!
this makes reporting bugs a joy. you report them, boom they're gone. yes!
fixing bugs is 10x faster when
you have no "deploy" step.
i just come to this page
and start changing a few lines
often even from my phone
we're merging with the machine
