Properly starts sessions loaded from another directory using Telescope.
Crucially, this version compares the working directory of the session, not
the working directory at the time of the session load, to the lists
of allowed and ignored directories.
Co-authored-by: Oli <olimorris@users.noreply.github.com>
* fix: TestFollowCwd
* fix: follow_cwd not actually working
cause: `follow_cwd and nil or session` always use `session` because the
`true and nil` expression is evaluated to false
* feat: add icons and colors to telescope picker
* feat: add configuration options for telescope icons
* fix: remove highlight group for telescope normal selection
* fix: properly resolve directories
The `vim.loop.fs_realpath()` function can be used to properly resolve
both the `.` shortcut as well as relative paths. This corrects scenarios
when opening nvim to a subdirectory of the working directory. With this
change doing so will properly resolve the session file to the directory
that was specified on the command line.
```console
$ pwd
/Users/username/.config
$ ls
fish iterm2 nvim
$ nvim nvim
```
This will result in using the path `/Users/username/.config/nvim` for
the session. The behavior will be the same as running plain `nvim` from
within the `/Users/username/.config/nvim` directory itself.
This change also quotes the path passed to `git` to properly handle
paths containing spaces.
This change also corrects some typos in the readme.
* fix: isdirectory is not necessary
The fs_realpath function will return nil if the path doesn't exist.
* fix: typos in comments
* fix: isdirectory is still necessary
Oops, the isdirectory check is necessary to confirm it's a directory and
not a file.
* Update logic for autoload or starting sessions.
The logic to prevent autoloading/starting sessions when any arguments
are supplied to neovim is to prevent session management from kicking in
when editing a single file.
This updates the logic to allow a single argument passed to neovim as
long as the argument is an existing directory. When neovim is launched
in this way it behaves the same as opening neovim with no arguments but
has changed the working directory.
This results in consistent behavior of the autoloading/starting of
sessions when passing a directory argument to start neovim.
See: https://github.com/olimorris/persisted.nvim/discussions/93
* Fix comment, make comparisons more direct
* Update functions to be directory-aware
The main functionality in `init.lua` assumes using current working
directory in most cases. This refactors these functions to allow passing
in a directory instead.
The default behavior is to now use the current directory unless neovim
was started with a single directory argument, using that instead.
This also special-cases `.` as `vim.fn.expand()` does not resolve that
to the current working directory.
* fix: unnecessary shell commands when autosave off
Problem: Shell programs aren't able to detect nvim exit.
Solution: Avoid running shell-commands unnecessarily on exit.
Programs that spawn nvim in-order to edit a file are unable to detect
nvim exit cleanly because of a race-condition that happens in
`VimLeavePre` and `get_current()` which runs shell commands during exit
even when `autosave` is off.
For example, using nvim nightly, run persisted.nvim with:
```lua
opts.should_autosave = function()
-- Do not autosave if git commit/rebase session.
return vim.env.GIT_EXEC_PATH == nil
end
```
And run `EDITOR=nvim git commit` from shell; git will fail waiting for
nvim to exit cleanly.
* fix: global variable in lowercase initial
When nvim is used as a man pager with `export MANPAGER='nvim +Man! '`, with autoload set to true, persisted.nvim still autoloads the current directory which is not desirable
Bryan
Oli Morris
Komil484
Mike Iversen
Christopher Speck
Jurek Olden
Zheng PiaoDan
Rémi Labeyrie
PostCyberPunk
Matthias Bilger
anhoder
Christopher Speck
Rafael Bodill
Beartama