[GNC] cut/paste problem in 3.4?

[Paul Kinzelman]

Hadn't thought of that.

I had already exited when I saw your suggestion and when I started
up gnucash again, that same sequence to/from the same accounts as before
now works. Perhaps copy/paste works only in the afternoons, not 
mornings. :-)

Earlier when I saw the problem, the cut did work,
the transaction vanished from the source account, but
when I pasted it into the destination account, it magically appeared again
in the source account but not the destination account.

I also tried cutting a transaction, then pasting into a text editor (emacs)
and the transaction does not paste so they must hide it someplace else
other than the standard clipboard.

I can cut/copy text from one of the gnucash fields and paste it in emacs
so that part works with the standard clipboard.

Anyway, thanks for the suggestion, I guess I'll chalk it up to a stray 
cosmic ray.

On 7/1/2019 2:56 PM, gnucash-user-request at gnucash.org wrote:
> Date: Mon, 1 Jul 2019 15:48:53 -0500 From: Adrien Monteleone 
> <adrien.monteleone at lusfiber.net> To: Users Gnucash 
> <gnucash-user at gnucash.org> Subject: Re: [GNC] cut/paste problem in 
> 3.4? Message-ID: <FB537A7B-ADBE-4268-BAC9-20E1C39BBD13 at lusfiber.net> 
> Content-Type: text/plain; charset=utf-8 Have you tried pasting into 
> something like a plain text editor after cutting? Perhaps the 
> clipboard is not picking up the ?cut? but GnuCash is still removing 
> the data. Anytime I have a pasting problem I always test in a plain 
> text editor to see if that is the issue. Regards, Adrien
>> On Jul 1, 2019, at 3:30 PM, Paul Kinzelman<paul at kinzelman.com>  wrote:
>>
>> I just tried cutting a transaction in one account, and I saw it vanish.
>> I went to another account, pasted it, and it wasn't there, it had
>> gone back to the account where it was before I cut it.
>>
>> So I carefully repeated the cut/paste and it did that again.
>>
>> So I deleted it from the one account, and typed it in manually into
>> the other account and it worked.
>>
>> Has anybody else seen anything like this?