Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tidy: Conflicted Copies - links to open in split view #570

Open
dwertheimer opened this issue May 8, 2024 · 4 comments
Open

Tidy: Conflicted Copies - links to open in split view #570

dwertheimer opened this issue May 8, 2024 · 4 comments
Assignees

Comments

@dwertheimer
Copy link
Collaborator

I have been using the /conficted copies command quite a bit, and I find one thing confusing. It opens the conflicted output and gives me statistics and a link to open the main note, but I don't see a note to open the conflicted copy. So I have to go dig around and find it in the sidebar.

Screen Cap 2024-05-07 at 20 07 16@2x

What would be better would be if you could create links that would open them each in split view, which is what I end up doing each time:
Screen Cap 2024-05-07 at 20 05 51@2x

thanks

@jgclark
Copy link
Collaborator

jgclark commented May 9, 2024

As best I understand it, this is not possible.
Otherwise I would have done this already.
Please re-open if you think there is a way to do this.

@jgclark jgclark closed this as completed May 9, 2024
@dwertheimer
Copy link
Collaborator Author

dwertheimer commented May 9, 2024

Why would this not be possible? Pretty sure you can use this helper:

Screen Cap 2024-05-09 at 10 29 35@2x

Just pass "splitView" for the 4th argument

@dwertheimer dwertheimer reopened this May 9, 2024
@jgclark
Copy link
Collaborator

jgclark commented May 10, 2024

Sorry, I misunderstood. I thought you were after opening the conflicted note (which I don't think is possible), not the recent addition of the conflicted copy of the note (which is possible, though doesn't make sense on iOS).

@dwertheimer
Copy link
Collaborator Author

dwertheimer commented May 10, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants