LivelyKernel / LivelyKernel/lively4-core

Text editor margin should be zero (or one)

Open
#333 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

comp: codemirror P4: nice to have
Dominant language
JavaScript
Stars
89
Forks
25
PR merge metrics
No merged PRs in 30d

Description

When editing code, and trying to place the cursor at the beginning of line, it is hard to see whether the cursor is at the very beginning or after one space. This is a screenshot when the cursor is at the beginning:

![lively](https://user-images.githubusercontent.com/197249/40798452-f1e8c13c-64bf-11e8-8733-53207bb99abc.png)

this is after one space:

![lively2](https://user-images.githubusercontent.com/197249/40798601-4c21ff06-64c0-11e8-9a82-5f3b1e2d0848.png)

and this is how it'd look in emacs:

emacs

I am not advocating to go with a block cursor, but if the left margin is just narrow (and the cursor may have to be a bit thicker), there would be less confusion.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not identify a file, test, or entry point. Start by locating the text editor's margin and cursor styling, then compare the rendering at the beginning of a line with the rendering after one space. Done means the left margin is zero or one space wide and the two cursor positions are clearly distinguishable.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.