`set clipboard=unnamed` not working

[brady444]

Please Review Before Posting!

• [X] I checked that the bug does not happen in the CodeMirror Vim demo. If it does, please report it there and not here.
  • Can't test the option there
• [X] I'm reasonably sure that this bug is indeed about the Vimrc file support and not a general Vim in Obsidian issue. If it's a general Vim issue, report it here.

Describe the bug:

Setting clipboard to unnamed or unnamedplus doesn't do anything.

To Reproduce:

Steps to reproduce the behavior:

• Put set clipboard=unnamed in your .obsidian.vimrc file
• See that Obsidian still uses a different clipboard for Vim copy/paste

Environment (please complete the following information):

• OS: Windows 11
• Vimrc plugin version: 0.10.2

Additional context:

Add any other context about the problem here.

.obsidian.vimrc:

set clipboard=unnamed

Plugin list:

[
  "obsidian-linter",
  "templater-obsidian",
  "tag-wrangler",
  "advanced-cursors",
  "table-editor-obsidian",
  "url-into-selection",
  "obsidian-map-view",
  "settings-search",
  "darlal-switcher-plus",
  "obsidian-kanban",
  "daily-notes-editor",
  "obsidian-link-embed",
  "simple-canvasearch",
  "obsidian-list-callouts",
  "vim-toggle",
  "obsidian-excalidraw-plugin",
  "local-backup",
  "obsidian-vimrc-support"
]

[brady444]

I also see "Vim is now set to yank to system clipboard." in the console

[ko-shin-ryo]

There’s currently a bug in the release version available from the Community Plugins list: when multiple Obsidian windows are opened at startup, only the first window correctly syncs with the clipboard.

If you’re using multiple windows, try closing all secondary windows and restarting Obsidian — that should temporarily avoid the issue.

This bug has already been fixed in the latest code on the master branch (see #249), but the fix hasn’t yet been included in the released version. If you can build the plugin manually, building from the latest source should resolve the problem.

[brady444]

Thanks, I built the plugin from source and it's working now. Why is the Obsidian version outdated?

[ko-shin-ryo]

@esm7 Do you have any plans to update the release version? I noticed that the same issue has also been reported in #265, and I believe it would be valuable to have the fixes from the current master branch included in a new release. I understand you must be very busy, so no pressure — just wanted to check in.

[esm7]

I was hoping @rsenna will take over as discussed here, but if not, I'll make sure to give these issues and PRs some attention soon!