as / a Goto Github PK

These cases should be handled without ambiguity

• The tag name
• full path (relative and absolute) path
• window name with a non-existent file
• trailing slash file
• mixed separator file
• uri/http/upspin
• anywhere where the intended CWD is different than the starting CWD of the process

Elastic tabstops look great on text, however, they will make problems for binary data. The options:

Implementation

• Do nothing
• Add Elastic, Keep Fixed
• Add Elastic, Remove Fixed

Runtime

• Scan files and file extensions, use elastic on source code
• Button in tag to pick Tab or Elastic

origin miscalculation leads to negative slice index

This will have to be fixed in as/cursor

Not sure this is an issue, but I get the following:

> go get -u -t github.com/as/a
# github.com/as/edit
c:\devenv\projects\_go\src\github.com\as\edit\lex.go:33:21: constant 9223372036854775807 overflows int

Reproduction

Edit ,a,bbbb\n,
Edit ,a,cccc\n,
Edit ,a,dddd,
Edit 2d

No Reproduction

Edit ,a,bbbb\n,
Edit ,a,cccc\n,
Edit ,a,dddd\n,
Edit 2d

insane resolution crashes linux clients

Should they be?

Dump: Save state of the editor to a file
Load: Load the state of the editor from a file

Specifically the unix shortcuts that delete a run of characters.

precondition: depends on #7 resolution

• Get/Put should disappear based on window state

main.go:142,143: act.SendFirst(edit.MustCompile(sc.Text()))
main.go:289,290: prog := edit.MustCompile(addr)
main.go:296,297: prog := edit.MustCompile(addr)
main.go:312,313: prog := edit.MustCompile(addr)
main.go:356,357: actTag.Handle(actTag.Body, edit.MustCompile(e.Addr))
main.go:470,471: prog := edit.MustCompile(s[5:])

investigating

Delcol does nothing, or just crashes the process

Edit x,^,i,#,

The traditional method for scroll+sweep is to transpose the background and foreground colors during insertion of new text. This is because the new text is being selected, so there is no need to highlight it again (just insert it with the right color in the first place). Currently, the logic in frame/win doesn't account for that. Text is inserted with the regular text color, and then repainted (which essentially means redrawn). A trivial performance improvement can be ascertained by fixing this.

[123] = mouse buttons
+ -> press
- -> release

Reproduction sequence
1+2+-3+-1-+-

win -> win
tag -> win
col -> ∀ tag ∈ col
grid -> ∀ col ∈ grid

The terminal emulator (i.e., the win program) is currently not implemented.

• Fix drawcache unionization
• Add membership test and short circuit tag handler
• Don't cache the cache: replace augmented frame.Draw call(s) with draw.Draw when dst is a cache

1: standard
2: red
3: green

bad clamp value clamps to global buffer