<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 2, 2016 at 2:01 PM, Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>El 02/06/16 a las 12:50, Walter Bender escribió:<br>
</p><span class="">
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jun 2, 2016 at 1:38 PM,
Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank"></a><a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Not every time you do an activity are you doing work
worth committing. For instance I work with a lot of
terminals, that I reuse and there's no point in
committing terminal sessions.</p>
<p>So imho Sugar should not force you to commit if you
don't want to.<br>
</p>
</div>
</blockquote>
<div><br>
</div>
<div>We had long ago talked about letting some activities
opt out. Regardless, adding the commit message back with
an opt-out button is fine with me, but I still don't
understand what problem we are solving. </div>
</div>
</div>
</div>
</blockquote></span>
Good question. I hope Tony can answer that. If I understood him
correctly he's trying to avoid having many journal objects currently
having exactly the same name thus being indistinguishable from each
other.</div></blockquote><div><br></div><div>As I mentioned in a separate thread, I think we need to think more w holistically about multiple users on a single Sugar instance. There are many solutions that come to mind. Why not have a way of selecting which user is active and making Journal entries that way?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>If I understand it, Tony also wants to circumvent the
relaunch last instance by default as well. In the case of
your Terminal example, it would mean you'd have Terminal
instances in your Journal for each time you used the
Terminal unless you too the time to go to the Journal and
search for a previous instance. I think that makes the
spam problem worse, not better.</div>
</div>
</div>
</div>
</blockquote></span>
I tend to agree with you on that one. Tony makes a valid point that
Sugar, more often than not, is used by many learners who may not
expect to open somebody else's work by default.<br>
<br>
Just a detail in your conclusion, is that, by having a `don't
commit` option, I would have probably no journal objects at all for
Terminal.<br></div></blockquote><div><br></div><div>So you would want to let the user explicitly not save the state of the Terminal, e.g. history, CWD, etc.? Not sure why, but in any case, this will probably require deleting the entry somehow on exit, since the entry is created long before the exit dialog.</div><div><br></div><div>-walter </div></div><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font><font>Walter Bender</font></font><br><font><font>Sugar Labs</font></font></div><div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br><a href="http://www.sugarlabs.org" target="_blank"><font></font></a><br></div></div></div>
</div></div>