Save cursor position within the note

tessus · 2018-05-04T00:57:11.561Z

The info could simply be saved in memory while Joplin is running.

That's true, but it wouldn't be persistent. The meta data approach has another advantage: it makes it even persistent between devices.

tessus · 2018-05-12T01:15:05.310Z

What do you think of adding the cursor position to the metadata when switching a note? Or maybe this can be a 2 step solution:

save position in memory
add position to meta data (this is not absolutely necessary, but has its advantages)

I can open a feature request on github and reference this topic.

laurent · 2018-05-12T10:15:47.313Z

Yes please open an issue with it and it would indeed be useful. I have no objection for the first step but the second one I’m not so keen as it feels more like app state. I think the issue is that it means every time you read a note, you will also modify it and it then will need to be synced.

tessus · 2018-05-14T00:04:29.105Z

laurent:

I think the issue is that it means every time you read a note, you will also modify it and it then will need to be synced.

This is partly correct. Every time you edit a note (or change the cursor position) a sync would be required. But since you already sync after every key stroke, this wouldn't be much of an overhead.
Just reading the note itself should not change the cursor position (unless the note is opened on a different device and the cursor position is not the same).

Anyway, I do understand your reluctance. The first step is sufficient for most cases. It's just that the cursor postions would be lost after restarting the app.

tessus · 2018-05-14T00:15:07.508Z

github.com/laurent22/joplin

Issue: [Feature Request] save cursor position

opened by tessus on 2018-05-14

/ref https://discourse.joplin.cozic.net/t/save-cursor-position-within-the-note
Summary:
Every time one switches between notes, the cursor position is reset to the top of the note.
When working with a...

enhancement

jidar · 2018-11-12T20:20:14.619Z

Any chance we can get another look at this issue? I note that it’s open in github, was queued up for the hackathon this past Halloween and then dropped.

I generally write very long notes (think of multi-month projects) and having to scroll all the way to the bottom every time I open a note is painful!

flatu · 2020-04-02T09:21:58.347Z

I second this request.

Nifaal · 2020-11-02T13:24:07.403Z

I'd love that too. I often use the web clipper to save article and read them later.
Remember the cursor position via meta-data would be ideal to me.

dfwdraco76 · 2021-01-11T21:33:12.775Z

I'd like to see this as well.

Discovered the issue via Retain Position Within Tab when Switching Between Tabs · Issue #19 · benji300/joplin-note-tabs · GitHub

philippelr · 2021-02-05T23:25:04.123Z

I would love this feature too. Working with long notes without it is painful.

outofstep314 · 2021-02-19T20:30:07.781Z

This feature would be useful for me as well. Although I notice some people were saying the cursor defaults to the top. On my device (details below), the cursor actually starts at the bottom of the note upon opening.

OS: Android 7.0
Joplin: Joplin 1.7.5

whitewall · 2021-07-25T05:03:41.346Z

I realize asking here may not be useful, but I'm wondering if there has been any progress on this. It looked like, from the initial posts, this would be an easy problem to solve. I've also read through the github issue, but it seems that it hasn't moved forward.

Any updates?

licuti1 · 2021-09-14T08:22:39.426Z

Hello Everyone. I would suggest to consider this improvement, because it is relatively annoying for long text management.

Regards and ciao

skim1124 · 2021-09-14T08:39:39.618Z

For me as well, this would be a higher priority than most feature requests because it directly affects workflow and efficiency.

rxliuli · 2021-09-14T09:32:18.376Z

I think this should belong to the core function like the tab page. . .

ken1kob · 2021-10-12T08:55:09.734Z

Through reviewing UX & UI of Joplin as a newly-coming user, I found some problems and am trying to solve some of them. One of the remaining is "scroll position is not remembered" discussed here.

The problem consists of two strongly related sub-problems:

(A) Scroll position is not remembered, when a selected note changes.
(B) Scroll position is not preserved, when the editor layout (Editor/Viewer/Split) changes.

I examined them using Joplin desktop app 2.4.9 and summarize here.

First, WYSIWYG editor has no problem. So, I talk about Markdown Editor and Viewer.

For (A) Note Change:

Layout	Result (preserved)	Result (moved to)
Viewer	Always	-
Editor	-	Always, top (mostly), middle/bottom (sometimes)
Split	Sometimes	Otherwise, as above

For (B) Layout Change:

From	To	Result (preserved)	Result (moved to)
Viewer	Editor	Always, with a little gap	-
Editor	Viewer	Sometimes, with a little gap	Otherwise, bottom
Split	Editor	Sometimes, with a gap	Otherwise, bottom
Editor	Split	Sometimes, with a gap	Otherwise, bottom
Split	Viewer	Always, with a little gap	-
Viewer	Split	Always, with a gap	-

Since most results are the mixture of preserved and not, it is difficult to examine them. To complicate matters, if a position looked preserved, it would be nothing more than moved to somewhere near the right place. This is the reason that many reports conflict (the problem occurs or not, and it can be reproduced or not).
Anyway, the problem is still alive and not solved.

I reviewed the existing forum posts and github issues, e.g. scroll position is not remembered · Issue #4797 · laurent22/joplin · GitHub. The issue is closed by PR#4806. The PR seems right to me, however, it fixes only one cause, and the other causes remain.

If needed, I'll tackle with this problem, after Sync-scroll Pull Request is integrated. How about it?

CalebJohn · 2021-10-13T06:55:17.443Z

Looks like there is decent pressure to get this fixed and you're already working in this space so I think you'll do a good job. I'm looking forward to seeing what you come up with!

ken1kob · 2021-11-11T12:34:36.810Z

Finally, Sync-scroll Pull Request is integrated.

Then, I try to solve the problems in the issue, Desktop: Scroll position is not remembered/preserved in Markdown Editor and Viewer · Issue #5708 · laurent22/joplin. And I'll report the progress there.

lukewlms · 2024-01-06T16:30:01.732Z

This would still be very useful (new user here coming from years of OneNote usage) but doesn't appear integrated. If I click a note then there is no cursor, and when I highlight the body the cursor is always at the top instead of where I left it. It would be much more useful if the cursor position for a note is remembered while it's in RAM. I don't personally need any more synchronization than that.

Thanks for the great product, so far the app and API are very exciting.

gmilowamw · 2024-06-25T17:26:32.570Z

This issue has resurfaced, 10195 is the Github Issue which is being closed due to lack of activity: