tag:support.multimarkdown.com,2013-02-12:/discussions/suggestions/2798-criticmarkup-exportMultiMarkdown Software, LLC: Discussion 2016-06-09T18:11:15Ztag:support.multimarkdown.com,2013-02-12:Comment/393144432016-03-05T20:16:11Z2016-03-05T20:16:11ZCriticmarkup export?<div><p>One of the things I am looking at for the Pro version of
Composer 3 will<br>
be the ability to manage "projects" consisting of multiple files.
I<br>
can't promise anything yet, but it is something I want (which
always<br>
increases the likelihood of completion. :)</p>
<p>As for the copy from HUD, I'm not sure that the workflow on that
makes<br>
sense to me. How do you see it working?</p>
<p>Fletcher</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/393144432016-03-06T10:50:28Z2016-03-06T10:50:29ZCriticmarkup export?<div><p>Poorly :)</p>
<p>Basically, what I was trying to accomplish was a text file that
included<br>
the results of a search in a criticmarkup hud. By way of example: I
have<br>
a bunch of text files with stuff scattered through them saying
things like</p>
<p>{>> @todo fix this section <<} {++ @edits add the
thing about boomerangs ++} {>> @todo make this suck less
<<}</p>
<p>What I was trying to do was copy and paste those to a separate
txt file.<br>
Which, upon experimentation, turned out to actually not be
particularly<br>
useful, because the primary thing the hud gets me is the ability
to<br>
click and go to that line. I actually have something set up for
this in<br>
vim using the quick fix list functionality, and if you would like
more<br>
details about how that works I'll be happy to share, but basically
I get<br>
a vim window with just that list across a directory and I can hit a
key<br>
on each line to open that file in a window at the line
referenced.</p>
<p>As one more note toward this I will say that while I have my
files in a<br>
single directory, I suspect this is probably a bit limiting for
some<br>
people's use cases, and defining a "project" may be one of the
more<br>
interesting problems here. Maybe a tag in the yaml frontmatter?
I'm<br>
probably the only person who would find that a good idea given
its<br>
interoperability with my other esoteric plain text voodoo...</p></div>Steen