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

Export of a conflict does not create a file #4095

Closed
Pete-C2 opened this issue Nov 16, 2020 · 3 comments
Closed

Export of a conflict does not create a file #4095

Pete-C2 opened this issue Nov 16, 2020 · 3 comments
Labels
bug It's a bug desktop All desktop platforms high High priority issues

Comments

@Pete-C2
Copy link

Pete-C2 commented Nov 16, 2020

Environment

Joplin version: 1.2.6
Platform: Windows
OS specifics: 7

Steps to reproduce

  1. Create a conflict between devices
  2. In the Conflicts section, right click on the conflicted note and Export Markdown
  3. The only results is an empty _resources folder (in this case I don't believe that there should have been any files), but NO markdown file.

Describe what you expected to happen

The conflicted note should be saved in the chosen folder as a .MD file.

Logfile

CommandService::execute: showModalMessage {message: "Exporting to "C:\bin\Joplin" as "md" format. Please wait..."}
C:\Program Files\Joplin\resources\app.asar\InteropServiceHelper.js:161 Export result: {warnings: Array(0)}
C:\Program Files\Joplin\resources\app.asar\lib\services\CommandService.js:141 CommandService::execute: hideModalMessage null

@Pete-C2 Pete-C2 added the bug It's a bug label Nov 16, 2020
@laurent22 laurent22 added high High priority issues desktop All desktop platforms labels Nov 16, 2020
@laurent22
Copy link
Owner

Most features aren't available within the conflict notebook because it's special, so there shouldn't have been any export item in there (I've now removed it). You could do what you want by first moving the note to a regular notebook.

@Pete-C2
Copy link
Author

Pete-C2 commented Nov 17, 2020

Since there is no way within Joplin to do a conflict comparison/merge, it would be more useful to be able to export conflicts. I resorted to editing the conflict (so that I could see the source markdown text), copying and saving as a markdown file, exporting the equivalent note and then using a file comparison application to find the differences so that I could copy the bits I needed.

@laurent22
Copy link
Owner

In fact it's easier to enable export for conflict notes than to disable everything, so it should work from next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It's a bug desktop All desktop platforms high High priority issues
Projects
None yet
Development

No branches or pull requests

2 participants