Re: [orca-list] Change made to flat review copy/append

[Nolan Darilek <nolan thewordnerd info>]

Strongly discouraged. There are circumstances where I'd want one 
behavior or the other. Making it a setting would just be a thing I'd 
have to flip back and forth based on what I want, and making the 
separator configurable would just be excessive.


I guess if I had to ask for something, and no one else is, I'd like to 
suggest that we revert the commit. Or maybe prepend a newline but don't 
append one when appending a new line to the clipboard (eek, that's hard 
to parse.) So you're still getting multiple physical lines, but no final 
newline. Maybe that would satisfy everyone for the time being?

On 1/27/20 2:00 PM, John Covici wrote:
> Could it be in the gui as a checkbox or to specify the separator in
> the gui?
>
> On Mon, 27 Jan 2020 14:20:22 -0500,
> Nolan Darilek wrote:
> > No need to apologize so much, thanks for all your work. :) I'm
> > not necessarily asking for anything. I can work around this for
> > the time being. Just noting that this broke my "I need to copy an
> > exception into an issue/email to coworkers" workflow, but clearly
> > the previous solution broke someone else's. Maybe we revert,
> > maybe we hold out for start/end markers. I don't know what the
> > best path forward is--I'm just contributing another data point to
> > help us all decide. :)
> >
> > On 1/27/20 1:16 PM, Joanmarie Diggs wrote:
> > > Understood re the marking solution. In the meantime, are you
> > > asking me to totally revert the change, partially revert the
> > > change, or make it possible to customize the separator
> > > character via orca-customizations.py?
> > >
> > > Sorry and thanks!
> > > --joanie
> > >
> > > On 1/27/20 12:41 PM, Nolan Darilek wrote:
> > > > So one thing this absolutely does break, and I don't know what
> > > > the workaround is, is copying exceptions. Here's an example of
> > > > one I just tried copying, trimmed down as to not be overly
> > > > annoying:
> > > >
> > > >
> > > > Recovering state to /tmp/skr_9101093002840883559 Exception in
> > > > thread "grpc-default-executor-0" java.lang.Error:
> > > > com.abbyy.FREngine.EngineException: Internal program error:
> > > > Src/PagesPrivateStorage.cpp, 49.     at
> > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1155)
> > > >       at ...
> > > >
> > > >
> > > > I.e. the whole thing on one long line.
> > > >
> > > > I guess now I have to store the exception in a file, load that
> > > > into gedit, and copy-paste out of that.
> > > >
> > > > I really do think the start/end-mark solution is the best
> > > > here. No amount of adding/removing newlines will satisfy
> > > > everyone, and even a setting will work in some instances and
> > > > not in others.
> > > >
> > > > On 1/22/20 6:57 PM, Mewtamer wrote:
> > > > > While I'm quite use to line-by-line cut and paste as a nano user, I do
> > > > > agree the copy, line down, append, line down, append process described
> > > > > sounds rather cumbersome.
> > > > >
> > > > > For those unfamiliar with nano, it's cut command takes the current
> > > > > line and puts it in a buffer, and repeated cuts append additional
> > > > > lines to the buffer until you move the insertion point or uncut the
> > > > > buffer's contents, after which, the next kut clears the buffer.
> > > > >
> > > > > Inspired by this behavior, perhaps one way to simplyfy multi-line
> > > > > copies in a way that can be implemented relatively quickly and serve
> > > > > as a stopgap until a marker or shift+arrows selection method can be
> > > > > implemented would be for:
> > > > > 1. Initial copy command copies current line and automatically moves
> > > > > the reading cursor down one line.
> > > > > 2. repeated copy commands without other input are assumed to
> > > > > be appends.
> > > > > 3. moving the reading cursor manually or issuing other commands
> > > > > assumes you're done copying.
> > > > > 4. The append command can be used to start copying from a
> > > > > different location.
> > > > >
> > > > > So, if copy were bound to Orca+c and append to orca+shift+C and you
> > > > > want to copy lines 2-5 and 10-15, this might simplify the process to:
> > > > >
> > > > > 1. Navigate to line 2.
> > > > > 2. Hold orca and tap c four times.
> > > > > 3. Navigate to line 10
> > > > > 3. Hold orca, press shift+c and tap c five more times(with or without
> > > > > releasing shift).
> > > > >
> > > > > The marker idea or simply being able to shift+arrow keys in flat
> > > > > review would probably be quicker if implemented, but what I just
> > > > > described still sounds quicker than the current method and is
> > > > > presumably just chaining together existing functions in a way that
> > > > > reduces keystrokes(essentially, a mini-macro). Admittedly, such might
> > > > > actually be a lot harder to implement than I think, but I figure it's
> > > > > worth mentioning as a possible intermediate improvement.
> > > > _______________________________________________
> > > > orca-list mailing list
> > > > orca-list gnome org
> > > > https://mail.gnome.org/mailman/listinfo/orca-list
> > > > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > > > Orca documentation: https://help.gnome.org/users/orca/stable/
> > > > GNOME Universal Access guide:
> > > > https://help.gnome.org/users/gnome-help/stable/a11y.html
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > Orca documentation: https://help.gnome.org/users/orca/stable/
> > GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html