Stateful Per-File Cursors?

Question

Stateful Per-File Cursors?

cmundi opened this issue 13 years ago · 4 comments

Is it feasible for nide to remember the last-known cursor position within a file and return to that position the next time the file is selected/opened? This would not have to persist across sessions.

Answer 1 · 2011-12-31T18:44:55.000Z

Hmm, yeah.

The CodeMirror editing component is currently destroyed whenever you switch between files. Perhaps we could just hide it?

To keep memory usage on a sane level, if there are more than a set number of components (say 10 or 20) we could just destroy the least recently used one.

Answer 2 · 2011-12-31T20:12:57.000Z

That sounds very reasonable.
On Dec 31, 2011 11:44 AM, "Marco Aurlio" <
reply@reply.github.com>
wrote:

Hmm, yeah.

The CodeMirror editing component is currently destroyed whenever you
switch between files. Perhaps we could just hide it?

To keep memory usage on a sane level, if there are more than a set number
of components (say 10 or 20) we could just destroy the least recently used
one.

Reply to this email directly or view it on GitHub:
#35 (comment)

Answer 3 · 2012-01-04T02:00:35.000Z

@cmundi: This is now implemented in master, and will ship with the next version.

Answer 4 · 2012-01-04T02:05:13.000Z

Pure genius. I am really enjoying nide on my current project.
On Jan 3, 2012 7:00 PM, "Marco Aurlio" <
reply@reply.github.com>
wrote:

@cmundi: This is now implemented in master, and will ship with the next
version.

Reply to this email directly or view it on GitHub:
#35 (comment)