Rune 1.1: adds Python, an Emacs editor, a symbol index and is now free

ernestrc an hour ago | parent | next [-]

Author here. We pushed 1.1 today. It was scheduled for release two weeks ago, but it was quite hard to balance adding so many new features with the influx of bug reports that followed our launch a month ago. Obviously, adding Python is a big one, but I'm most excited about the new symbol index, which reduces 10-second workspace-wide queries to under 100 ms. The agent also uses this index, so the benefits compound over long agentic sessions as well. FWIW I'm not quite sure about the black-and-white dimming feature. If it's not useful, we might remove it in a future release so please let us know!

▲

esafak an hour ago | parent [-]

Is there a short video walkthrough for newcomers?

	▲	ernestrc 27 minutes ago \| parent [-]
		Not a walkthrough video, no. The first steps section of the getting started guide is the best place to start (https://docs.rune.build/#your-first-steps). There are also a few short clips on the home, Go and Python pages. Fair ask though! a short walkthrough is on the list.

▲

bryanlarsen 23 minutes ago | parent | prev | next [-]

Quite impressed with a sales page basically telling me to stick with Emacs for now: https://rune.build/coming-from/emacs

	▲	OhSoHumble 15 minutes ago \| parent [-]
		> Org mode, Magit, TRAMP, or another deep Emacs-native package is your center of gravity This is me. > rewriting the editor live in Elisp is the whole point for you Funnily enough, this is not me. I just grab Doom Emacs and do very minor adjustments. I just really like all the packages and the ecosystem.

▲

cobolexpert 17 minutes ago | parent | prev | next [-]

Any connection to https://github.com/CeleritasCelery/rune ?

▲

callistocodes an hour ago | parent | prev [-]

Page crashes with “a problem repeatedly occurred on $page” on iOS Safari, just fyi

	▲	ernestrc an hour ago \| parent [-]
		Thanks, looking into it. edit: I think it's from all the videos playing at once, even when not visible. It should be fixed now.