How should Micro respond to a directory name in the CLI input?

[SoleBridge]

How should Micro respond to micro dirname/?

• I think it would be useful if micro would change it's working directory if presented with a directory name on startup.
• An example use case is being in the project's outer scope, running micro src/, to open micro in the source dir.
• This would allow a good starting point for opening files, using the filemanager plugin, etc.

1. Is this something other users / maintainers are interested in?
2. Could this cause some nasty side effects?
3. Is there a more useful way to handle this case?

I'm currently playing with the code to see if this works and is useful.
Looks like some code could be added to the section where input files are loaded.
If others are interested, I can make a pull request :)

[Andriamanitra]

I'm not necessarily against the idea but I have a few concerns:

• Getting an empty buffer could be confusing to users who were trying to open a file.
• What happens if you provide multiple files/directories to open? Eg. micro dir/a dir/ b dir/c dir2/ d could be quite confusing and unexpected depending on how the feature is implemented.
• What's the benefit of micro src/ over cd src; micro or env -C src/ micro?

[SoleBridge]

1. Yeah, I guess so.
2. In my implementation, I am only using the first directory, ignoring all others.
3. I came up with the idea because I was jumping between projects, and thought this would be a nice way to open a single project at a time without having to cd a; micro ... cd ../b; micro.

In the same idea, I was also thinking it would be cool if there was something like a .micro file, to store info on which files were open and on what tabs, to "restore" a session; I should explore available plugins.

Side note, I wanted to try doing the chdir() thing first to explore the project and how the codebase works, and thought it might be useful to share the idea.

[Andriamanitra]

In the same idea, I was also thinking it would be cool if there was something like a .micro file, to store info on which files were open and on what tabs, to "restore" a session; I should explore available plugins.

That's a great idea for a plugin but .micro file extension is already used by colorschemes, maybe go with something more explicit like .micro-session.

[cutelisp]

FYI, personally I never tested it but seems there's already a session plugin