Hi, actually I had to look a bit found it because I didn't find it. Then I read the source code and finally 'found' it. Maybe others may have also some thoughts about that.
''special context menu'' is certainly the best practise IMHO. This would keep the interface lean and elegant. BTW, thanks Thomas and Meik that you are working on this! Highly appreciated! Kind regards Stefan On October 13, 2018 8:59:00 PM GMT+02:00, meik michalke <meik.micha...@uni-duesseldorf.de> wrote: >hi, > >Am Samstag, 13. Oktober 2018, 13:59:34 CEST schrieb Stefan Rödiger: >> indeed a great thing! All tests worked well here. > >that's great to know! > >> A general remark on RMarkdon in RKWard. Methinks, RMarkdown is more >like a >> method/philosophy than just a functionality. Rmarkdown is in data >science >> with R very intensively used. Why not put it as separate menu entry >on a >> prominent place? Right now there is great functionality (the preview >& and >> plugin) and more seems to come. > >interesting thought. but doesn't it make more sense to have the export >menu >for RMarkdown files where all other export options usually are? i.e., i >didn't >even tell you where to look but it seems you were able to find and use >it. > >i can however see that it can be helpful to have a special context menu >if the >currently active editor window is markdown, including a direct launcher >for >the export plugin. so i wouldn't add a new permanent menu category, but >rather >let RKWard detect the file type and produce a context sensitive submenu >like >it already does for R code, help pages or data frames. > > >viele grüße :: m.eik > >-- > dipl. psych. meik michalke > institut f"ur experimentelle psychologie > abt. f"ur diagnostik und differentielle psychologie > heinrich-heine-universit"at d-40204 d"usseldorf -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
