Moving to a data format that makes a stronger distinction between content and envelope might be nice. JSON would work if content is actually quoted (don't bet on it). A directory would probably be better because the content of a file can't break the meta-data in the directory. Something like a real database would be even better.
Let's all blame Telnet and FTP for starting this lamentable trend of mixing text and meta-data, but it would be nice to stop reliving five decade old problems. On Sat, Apr 13, 2019 at 8:48 AM Sam Ruby <ru...@intertwingly.net> wrote: > On Sat, Apr 13, 2019 at 7:29 AM Shane Curcuru <a...@shanecurcuru.org> > wrote: > > > > Sam Ruby wrote on 4/12/19 9:48 PM: > > > On Fri, Apr 12, 2019 at 2:42 PM Sam Ruby <ru...@intertwingly.net> > wrote: > > >> > > >> 3) Somebody uses the whimsy board agenda tool to update the incubator > > >> report, and it dutifully strips out the previous report (up to said > > >> row of dashes) an inserts a new report. > > > > > > Here is the regular expression in question: > > > > > > > https://github.com/apache/whimsy/blob/00d8c5d473beae972138e6c1b3bac2633b6ea342/www/board/agenda/views/actions/post.json.rb#L118 > > > > Thus, a key short term solution is to never put lines of 40 dashes in > > the Incubator report, right? > > +1. Or at least avoid starting a line of dashes in column 1. Indent > the dashes and you still have a visual separator without it looking > like a report separator. > > - Sam Ruby > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
