Request for comments:

When you're authoring text, or code, do you have keybindings that make use of meta or super key combinations?
In Gopherine I need to add support for a few keystrokes related to hypertext editing that have no equivalent in any of the traditional keymaps (not in emacs, vim standard configs at least)

1/2

#gopherine #gopher2049

For example, say I am using the vim keymap and I enter Insert mode to change hypertext content of a page I'm viewing, and I need a keystroke to move between multiplexed text lines. For one line of text, I have parallel data in parallel streams for the same line, and I need keystrokes to move to the previous and to the next stream.
I am currently using Super + Right Arrow for Next Stream, and Super + Left Arrow for Previous Stream.
Does that make sense to you guys?

2/2
#Gopherine #Gopher2049

@h Vaguely reminds me of "show codes" in WordPerfect.
@vertigo @h that but even more it feels like a comment block in a traditional #Forth block editor. #ForthOS from Andy Valencia uses that (it can be easily started in qemu)

@h @vertigo I have managed to rebuild my #ForthOS and make screenshots of the built-in text editor (vi-like). There is one command (ZS) to switch between a normal screen (code ) and a shadow screen (comments): https://mastodon.social/media/zRKsFuCUT02EkxDVRYY https://mastodon.social/media/Ez_4bCuB34FNI15xKOs

That is how two alternate streams are handled in a classic Forth block editor

http://forthos.org/vi.html

ForthOS Editor

ForthOS editor

@saper You may not know this, of course, but @vertigo and I are ong time Forth programmers, and in Vertigo's case, he has written a number of Forth compilers for the computers he designs ad makes from scratch.
I've consdered writing a new high performance Forth compiler myself for the hypermedia project I've been discussing. So, yes, Forth and Forth tools are definitely welcome inspiration.
@h @vertigo Cool! I was wondering, if a multi-screen editor could be helpful for hypertext
@saper Yes, there's always bits of inspiration to borrow from different implementations. It's difficult for m to express in words, typing on a tablet what it's going to look like and I've meanng to start a blog soon. I jst want to make sure I have enough content ready before I do, so I can avoid the dread effect of feeling pressured to write on a deadlne, something that ievitably results in writer's block.
@vertigo
@saper To put it succinctly, he eiting mode is going to be very minimalist at first. Third partes will eventually be enabled to develop extensions on it. Visually-wise there's going to be continuous contexual hints, and metadata will look in expanded readaable form for the current line, paragraph, or code block, with less data being displayed for more distant blocks as they recede in the past when you scroll down, provding only context cues for the text that is more distant
@saper By default, this won't look like a split screen, or at least the visuall cues and hyper context of linked texts won't occupy the full area of a split window, it will look more like a pane frame on the right side of the current block or paragraph. This context pane will have different possible views, including one that displays adjacent hypermedia context ina graph-theoretical live view.
@saper Of course some of these things aren't possible in a traditional text terminal. I'm hoping that new ways of seeing and interpreting text will offer back some bits of inspiration for other hypermedia developers as well. As much as I absoutely love the Unix tradition we must explore some new directions for some things. It's like leaving the home of our parents when we grow up. It's time.
@saper The main problem I have right now is in figuring out how to provide a familiar environment for users so it doesn't feel like a completely alien world to them.
It's useful to me to learn what looks like a familiar world to other people.
Please keep ideas coming!