micro-editor / micro-editor/micro

symbolic links are sometimes replaced with a normal file

Open
#3,016 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
29.6k
Forks
1.4k
Avg merge
2d 18h
Merged PRs (30d)
10

Description

Description of the problem or steps to reproduce

I store my config files (bindings.json and settings.json) in Dropbox and I put symbolic links on them in my ~/.config/micro folder. The advantage is that my settings are automatically synced on all my machines.

However, when I edit these files via the symbolic links, sometimes they are replaced with a normal file, i.e. with the normal file where the links pointed. After editing, they are not symlinks any more but normal, regular files. So in this case I need to upload to Dropbox the current version, delete the file and make a symlink on the Dropbox version.

My folder ~/.config/micro is on my local machine, not in Dropbox. In this folder I have symlinks pointing to some files in Dropbox.

It's a strange thing because it doesn't happen all the time. Sometimes the link remains a link after editing it.

Version: 2.0.13
Commit hash: 68d88b57
OS: Manjaro Linux
Terminal: wezterm

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by editing symlinked bindings.json and settings.json from ~/.config/micro, comparing cases where the link is preserved or replaced. Start by tracing the editor's file-save behavior for symbolic links; done means edits consistently preserve the symlink and update its target without replacing it with a regular file.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.