My Wish List:1. Custom "segregable" (color/grouping/separate-lines/etc) file/buffer tab displaysI often find myself working with similar-named files from multiple projects at once, often comparing differences between the same-named files. Recent VisualStudio (V13 onwards, IIRC) offers different "types" of tab groups (grouped by end, grouped as separate lines, etc.) and it would be nice if users could segregate open files in a similar manner in SE. Clarifying, I am not asking here for multiple projects at once (that's a different ask), this is strictly about supporting new means of grouping/segregating file tabs in the file tab display(s).
Ideally, I'd like a system where I could run a set of arbitrary user-set ordered rules against a newly-opened file (or buffer) in order to assign it to different filetab "groups" (or assign different attributes, like color). Attributes/grouping options would include {left, middle, right} in tab line, tab color, tab text attributes, separate tab lines, and so forth. Conceptually similar to where Visual Studio is going with tab handling, or where VisualStudio third-party extension
"VisualDocs" allows with their custom tab display.
As a stretch goal, allow users to open multiple "file collection" windows/panes across multiple monitors (with distinct sets of filetabs), and allow them to use rules to segregate both window to use and how to configure filetab.
2. Support for "Peek"-type view displaying definition/declaration/etc.VisualStudio 2015 (V14) has provision now when user wants to see associated definition/declaration, instead of having to open distinct file buffer, it can temporarily pop up an overlay which shows the file containing the relevant definition/declaration, in a scrollable view, but which disappears upon next editing action into main view. This allows quick perusal of references without causing overpopulation of open files (nor disruption of filetab schema). Doing so is much more real-estate effective, IMO, than the "open ref file as normal tab, but on right end of tab line, and close on next lookup action used with VisualStudio2013 (IIRC).
3. Elastic TabstopsSee
Nick Gravgaard's article and discussion of them here. This would be _very, very_ useful, esp. if it could properly interoperate with other implementations.
4. Allow multiple open projects/workspaces at onceThis was always kind of inevitable, wasn't it? Unless/until #1 is implemented, perhaps give different projects'/workspaces' files their own tab lines. Once #1 exists, allow rules to use "project"/"workspace" as differentiator in rule generation.
That's all for now, thanks as always for all the hard work!!