search

atom / bookmarks

Bookmark editor lines in Atom
MIT License
49 stars 36 forks source link

List all bookmarks in project #88

Closed jinglesthula closed 5 years ago

jinglesthula commented 7 years ago

Currently bookmarks:view-all only lists the bookmarks in the current buffer.

A hierarchical UI would be a necessity. Currently the list is flat, which works fine for one buffer. With arbitrary directory structure, some thought would need to be put to how to represent all bookmarks in the project in an easily navigable way (maybe using a foldable tree?)

It might be nice to show the complete list and allow type-to-filter on it as well. This would make projects with more than a handful of bookmarks much more navigable.

cortner commented 7 years ago

This - together with named bookmarks #34 and jumping to bookmarks across files would make my day

Daijobou commented 6 years ago

+1

jinglesthula commented 5 years ago

Just tried setting bookmarks in different files and bookmarks:view-all is showing all of them. Anyone know if this has changed since this issue was opened? It may have always been that way and I just missed it the first time around.

The "all" list also does have a type-to-filter input. It looks like the only thing in this issue missing is the hierarchy. Does anyone feel strongly about providing a way to structure the "all" list differently to allow for better parsing? If not, I'm good closing this issue, as that would be the only reason to keep it open.

rsese commented 5 years ago

Just tried setting bookmarks in different files and bookmarks:view-all is showing all of them. Anyone know if this has changed since this issue was opened? It may have always been that way and I just missed it the first time around.

Not sure off the top of my head but it does look to work as you described in 1.33.0.

It looks like the only thing in this issue missing is the hierarchy. Does anyone feel strongly about providing a way to structure the "all" list differently to allow for better parsing? If not, I'm good closing this issue, as that would be the only reason to keep it open.

:+1: we'll go ahead and close. Though this sounds pretty neat, it's likely not something the team would work on but also seems like a nice idea for a community package.