Idea: over command #201

New Issue

sloum · 2020-11-14T19:43:23Z

sloum commented

2020-11-14 19:43:23 +00:00

The idea here is similar to forth's over word.

Lets say that the client history looks like this:

1 - somesite/main.gmi (on line 23)
2 - somesite/posts/23.gmi (on line 37)

You may want to continue browsing, but not lose your place in 23.gmi. Without tabs, there is no way to do this in the present design. I am against adding tabs to Bombadillo. But over or jump could achieve the desired effect.

In the current state, to keep browsing off of the main.gmi file I'd need to go back, or manually type in the address. Then if I navigate I lose 23.gmi from my navigation history.

So what this new command would do is copy the history entry underneath the current entry and place the copy above the current page (placing you on that entry). So the history would look like this:

1 - somesite/main.gmi (on line 23)
2 - somesite/posts/23.gmi (on line 37)
3 - somesite/main.gmi (on line 23)

This lets us keep navigating while having access to a page we want to keep in our navigation history, including page state (what line we were on) for both the page we want to keep and the page we want to navigate from.

In theory this could take an optional param that would allow an arbitrary copy to the top of the history stack.

I feel like this is a hard to explain feature, but would be really useful. What do you think @asdf ?

The idea here is similar to forth's over word. Lets say that the client history looks like this: ``` 1 - somesite/main.gmi (on line 23) 2 - somesite/posts/23.gmi (on line 37) ``` You may want to continue browsing, but not lose your place in `23.gmi`. Without tabs, there is no way to do this in the present design. I am against adding tabs to Bombadillo. But `over` or `jump` _could_ achieve the desired effect. In the current state, to keep browsing off of the `main.gmi` file I'd need to go back, or manually type in the address. Then if I navigate I lose 23.gmi from my navigation history. So what this new command would do is copy the history entry _underneath_ the current entry and place the copy _above_ the current page (placing you on that entry). So the history would look like this: ``` 1 - somesite/main.gmi (on line 23) 2 - somesite/posts/23.gmi (on line 37) 3 - somesite/main.gmi (on line 23) ``` This lets us keep navigating while having access to a page we want to keep in our navigation history, including page state (what line we were on) for both the page we want to keep and the page we want to navigate from. In theory this could take an optional param that would allow an arbitrary copy to the top of the history stack. I feel like this is a hard to explain feature, but would be really useful. What do you think @asdf ?

sloum referenced this issue

2020-11-14 23:50:20 +00:00

Adds a jump command #202

sloum commented

2020-11-14 23:51:12 +00:00

I have opened a PR with this in #202

It was shockingly easy to implement and has already been really useful for me.

I have opened a PR with this in #202 It was shockingly easy to implement and has already been really useful for me.

sloum closed this issue

2021-01-22 05:57:49 +00:00

Sign in to join this conversation.