Open lcolladotor opened 5 years ago
Resolving changes in Word and then de-rendering is my preferred workflow, but I don't think it should be everyone's. I don't think resolving changes in the redoc_diff()
view is likely, though. Instead, these should happen in the text editor. There's some ways to make this easier, tough.
1) Syntax highlighting in the editor. This actually requires a PR to RStudio to change this file to pick up CM syntax: https://github.com/rstudio/rstudio/blob/8af730409bb6d651cc8f6816d136bea91441e7a4/src/gwt/acesupport/acemode/markdown_highlight_rules.js . If they agree, then a theme could be included in this package to highlight those sections.
2) An RStudio add-in with keyboard-shortcuttable commands like "Accept", "Reject/Remove Comment", "Accept and move to next", "Reject/Remove Comment and move to next", "Accept all", "Reject all", "Resolve all comments." It could also include commands for creating CM markup.
I'll add these to the list, but both are definitely things I could use help with and aren't too in the weeds of the current code base, so happy to accept PRs.
Hi Noam,
This issue is related to https://twitter.com/noamross/status/1129423451234668547.
Using
redoc
version 0.1.0.9000 and MS Word for Mac version 16.16.10 (190512), I found no way to accept or reject changes from the CriticMarkup syntax in an Rmd file. Maybe you would like users to interact with changes in the MS Word version, resolve them there, then useredoc::dedoc()
once that's all done.If you are interested in supporting a way to resolve changes, I would imagine that some type of browser-like viewer that is similar to interfaces for resolving git conflicts would be useful (choose option A --aka left--, option B --aka right-- or make your new option C).
There's also some of this functionality already in the CriticMarkup TextMate addin (which I then modified so it would work a bit with Rmd files) at https://github.com/lcolladotor/criticmarkup.tmbundle forked from https://github.com/DivineDominion/criticmarkup.tmbundle. The accept code basically is this one: https://github.com/lcolladotor/criticmarkup.tmbundle/blob/master/Support/bin/accept_critic.rb which is a series of gsub calls. I believe that it's not 100% complete for all the CriticMarkup syntax cases. These could be RStudio addins (similar to TextMate Bundle commands) and are likely easier to code than the git conflict-like interface. Though just stating in the documentation that users should resolve changes in the MS Word version could be ok too ^^.
Best, Leo
Session info