You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v3.0, Neo-tree has not changed the default config options, only adding to it. However, there are some new features that seem fairly uncontroversial to enable by default to reduce the (rather insane) amount of configuration that a user might want to do, out of the box.
One idea is to push a small v4.0 major patch that simply updates some defaults to be more user-friendly and trims out some deprecated code. A full overhaul of configuration, tree rendering, state management, etc, could be left for a v5.0.
Examples being:
the symlink_target component seems pretty useful to enable by default to indicate whether a file is/isn't a link
file icons probably shouldn't inherit the hidden/filtered highlight (like VSCode)
doing away with the custom "NC" popups and instead relying on winborder (or defaulting to rounded/config option when not available)
built-in trash binds/management (to be added) as the default instead of delete
Please suggest additional defaults you think are reasonable to change.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Since v3.0, Neo-tree has not changed the default config options, only adding to it. However, there are some new features that seem fairly uncontroversial to enable by default to reduce the (rather insane) amount of configuration that a user might want to do, out of the box.
One idea is to push a small v4.0 major patch that simply updates some defaults to be more user-friendly and trims out some deprecated code. A full overhaul of configuration, tree rendering, state management, etc, could be left for a v5.0.
Examples being:
winborder
(or defaulting to rounded/config option when not available)Please suggest additional defaults you think are reasonable to change.
Beta Was this translation helpful? Give feedback.
All reactions