apropos of Rich's observations above, I posted the following on the Joplin Discourse page: This may be a bug. If it isn't, it's jut not very intuitive. I had a similar problem: if I had the external editor set to /Applications/BBedit.app in Joplin's Preferences, then every time I tried to use the external editor, BBedit would spin up a whole new instance of the application and reproduce the state of the one already open, complete with duplicates of all open windows and documents. I tried setting the external editor to /usr/local/bin/bbedit with a variety of arguments, and that didn't work at all. What worked was to to leave the external editor setting in Joplin's preferences blank and set bbedit as the default editor in the shell configuration (in my case .zshrc) by adding the line setenv EDITOR "bbedit -w". Now when I ask for the external editor in Joplin, Joplin does the right thing: looks for the default editor and sends the note there. The note opens as a new document in the frontmost window of the running instance of BBedit.
On Tuesday, November 17, 2020 at 5:23:31 PM UTC-8 Matt wrote: > Mainly because I had a lot in Evernote that I was able to import, and it > handles the resources/attachments that went with my notes. It's open source > and hopefully will be around for awhile, but I have had some issues with > syncing lately, and I may move in the direction of folders and markdown > files. > > On Monday, November 16, 2020 at 9:56:24 PM UTC-5 Greg Raven wrote: > >> If you're using BBEdit, why use Joplin? Why not have a project with >> whatever folders you need, and create your notes in Markdown? With a little >> forethought, you can make your entries in such a way that project-wide >> search finds whatever you want. The best thing is that you are not locked >> into a proprietary program. Not to cast aspersions on Joplin, but many of >> these smaller software companies tend to disappear. By using Markdown files >> in BBEdit, there's virtually no way you would ever lose your notes. >> >> On Saturday, November 14, 2020 at 6:35:37 PM UTC-8 Matt wrote: >> >>> I'm trying to get BBEdit configured as the external editor for Joplin >>> <https://joplinapp.org/> and so far not having much luck. I saw on the >>> Joplin Discourse forum that another user encountered the same issue >>> <https://discourse.joplinapp.org/t/bbedit-for-osx-as-an-external-editor-is-empty/3357>, >>> >>> which is that BBEdit will launch but then not display the contents of the >>> text file. That person who asked in Joplin's forum had switched to using >>> Atom, but it was proposed that there might be a command line flag that >>> BBEdit needs, and I wanted to check here. I could not figure out what would >>> be needed. If I use /Applications/TextMate.app or >>> /Applications/FoldingText.app as paths, everything works as expected. The >>> only configurations options in Joplin for editors are path and argument. >>> Since BBEdit is launching, I know I have the path correct, and I confirmed >>> it has full-disk permissions. Any ideas would be helpful, or also to know >>> if the way Joplin handles external editors just won't work with BBEdit. >>> >> -- This is the BBEdit Talk public discussion group. If you have a feature request or need technical support, please email "[email protected]" rather than posting here. Follow @bbedit on Twitter: <https://twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/1b45f161-bab7-49cd-9fd0-9fda25e74ebdn%40googlegroups.com.
