[GNC] Flatpack GnuCash v3.2 available in Linux Mint and flathub website

[DaveC49]

Gnucash V3.2 is available in the Software Manager in Linux Mint 18.3
downloading from the flatpack form from the flathub
website(https://flathub.org/apps/search/GnuCash).

Installs OK and indistinguisable from my own build on my system. Can be
downloaded from the flathub site directly if you're not on Linux Mint. 

The flatpack runs as  /usr/bin/flatpack --b. Not sure how that handles other
flatpack software? This is my first flatpack installation. whereis gnucash
does not return anything so the flatpack obviously hides the installation.

The flathub version may be a good option for Linux users not interestedin
building from scratch but wanting the latest stable version. It seems to 
distribute up to date Linux packages independent of the distribution
packagers, which some recent posters have been seeking. 

David Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Building v3 - Wiki entry for Ubuntu

[DaveC49]

Hi Colin,

I'm responsible for m,ost of the update  on the build Ubuntu. No problem for
me with a more generic page name at all. I had stuck with the names that
were there as I updated it with the more recent build instructions. I have
tried to generalise the page and make it a bit more user oriented and less
specifically developer oriented than it was originally.

I have always wondered about the /usr/local/ as I also personally have a lot
of home built software which installs there by default and the Ubuntu File
System Heirarchy lists the two most common install points other than the
users home directory as:

/opt :- This directory is reserved for all the software and add-on packages
that are not part of the default installation

/usr/local :- The /usr/local hierarchy is for use by the system
administrator when installing software locally. It needs to be safe from
being overwritten when the system software is updated.

Please feel free to modfy the text as you feel fit. I did not find the FHS
exactly illuminating.

The Linux Mint and I presume Ubuntu distribution versions of GnuCash install
into /usr/local. I have always installed there and as long as I don't
install over it from the software manager, it has never been a problem for
me. I modified that from an earlier version which primarily recommended
installing into $HOME/.local as the preferred option. I do use that if I
have built a version from the  github master or maint for testing so it was
possibly more developer oriented. T times I have had 3 versions of GnuCash
up and running

David
Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[David Cousens]

On Wed, 2018-07-04 at 14:54 +0200, Geert Janssens wrote:
> Op dinsdag 3 juli 2018 00:59:51 CEST schreef DaveC49:
> > 
> > Geert,
> > 
> > I had realised the same thing about needing to uninstall before
> > building and
> > shifted the section on uninstalling to before the section on
> > Building on
> > the Wiki page and specifically mentioned using the previous
> > version's build
> > directory. I might make the note clearer about retaining the build
> > directory for uninstalling.
> > 
> Thanks for documenting all this.

No problem my pleasure
> 
> > 
> > From the tarball the source directory installs with the version
> > number
> > attached (from github it is a generic gnucash). It has become my
> > practice to
> > put the build directory inside the source directory (I have had no
> > problems
> > with that) so it is clearly identified which version it is for, or
> > alternatively one could tag the build directory with the version
> > number as
> > there is no real need to keep the source directory once the build
> > is done.
> This is a subtlety I'm not so sure about.
> I think in order for "make/ninja-build uninstall" to work properly
> you need to 
> keep both the source directory and the build directory. In addition
> the source 
> directory should reflect the version of gnucash you wish to
> uninstall.
> 
> Here's a quick experiment to illustrate this:
> I have a build directory outside my source tree and I have
> successfully run
> ninja-build install

Geert,
You are correct here. I tried the experiment and build.ninja looks for
the CMakeLists.txt in the top level of the source directory and fails
when it is not there. It also goes into the source tree. I copied
CMakeLists.txt back and then it failed when files further down the
source tree were not present
> 
>  This also means cmake will check dependencies
> before trying to run "make uninstall". The uninstall command depends
> on "install_manifest.txt".
> That file seems to be a file generated and tracked by the cmake build
> system itself. Our CMakeLists.txt files don't manipulate it
> explicitly. And clearly cmake attempts track dependencies on this
> file (namely each file that got installed).
The install_manifest.txt file is written by cmake_install.cmake which
is in turn called by the uninstall target in build.ninja which reside
in the top level of the build directory
> 
> > 
> > I'm not pushed for space so I don't bother to delete the source
> > files until
> > I've installed another version and I'm happy with it but others
> > won't
> > necessarily have that luxury.
> > 
> > At the moment the uninstall from a ninja build I did is a kludge. I
> > will see
> > if I can find how/where cmake generates the install secion when
> > creating
> > build.ninja and populate the uninstall target. If I succeed, i'll
> > generate
> > a patch.
> Are you referring to the fact that uninstall doesn't remove empty
> directories
> Maybe that can be improved indeed. I don't know. Keep in mind the
> intended final install destination is typically into a set of 
> directories that already contain applications and libraries. 
> So we can't unconditionally delete all directories. We should at
> least verify whether they are empty or not.
> And we probably don't want to delete any common top-level directory 
> like bin or lib when dealing with standard install locations.
>  

No. The uninstall target in build.ninja as written by cmake was just an
empty stub. It was originally:

#
# Utility command for uninstall

build uninstall: phony CMakeFiles/uninstall

#

 I copied the code from the install target:

#
# Utility command for install

build CMakeFiles/install.util: CUSTOM_COMMAND all
  COMMAND = cd /home/david/Applications/gnucash-3.2/build-ninja &&
/usr/bin/cmake -P cmake_install.cmake
  DESC = Install the project...
  pool = console
  restat = 1
build install: phony CMakeFiles/install.util

#

, substituted "uninstall" for "install" so it became:

#
# Utility command for uninstall
build CMakeFiles/uninstall.util: CUSTOM_COMMAND all
  COMMAND = cd /home/david/Applications/gnucash-3.2/build-ninja &&
/usr/bin/cmake -P cmake_uninstall.cmake
  DESC = Uninstall the project...
  pool = console
  restat = 1
build uninstall: phony CMakeFiles/uninstall

#

and then ninja uninstall works in a shell open in the build directory.

cmake_uninstall.cmake existed and had been created by cmake when it
configured the build, but it could not be executed from build.ninja.
Somewhere in the CMakeLists.txt files in the source something is
missing which writes the code into build.ninja to run
cmake_uninstall.cmake. 

I think it would be nice to tidy up the uninstall of the directories as
well. John has pointed out elsewhere 

[GNC] Alphavantage quote displaying wrong currency and value

[Mark Blakeney]

Hi,

I'm new to gnucash and trying to set up online quotes via Alphavantage. I
am using Arch Linux with stock versions gnucash 3.2-1 and
perl-finance-quote 1.47-1. I have my API key configured etc and gnc-fq-dump
works correctly as seen at https://imgur.com/a/swf5xto.

I have the stock configured in gnucash as https://imgur.com/a/mblUFvj. My
default currency is Australian dollars (AUD) everywhere.

However the online quote is displayed with the wrong currency (US) and
value as seen at https://imgur.com/a/gnS8Aau.

Does anybody know why?
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GNC List and DKIM (was Re: how to share style sheets between computers in GnuCash 3.1?)

[Robert Heller]

At Fri, 06 Jul 2018 09:47:52 -0400 Derek Atkins  wrote:

> 
> Hi Mark,
> 
> Geert Janssens  writes:
> 
> >> BTW I get a lot of DKIM rejection reports from recipient servers when I
> >> send mail to the list.  Is that because the list server strips the
> >> anti-spam headers from my message before it forwards it out?  Maybe there
> >> is a patch for that.
> >> 
> > I don't know. This is something our mailing list adminstrator may know more 
> > about... Forwarding back to the list...
> 
> Could you forward me one (or more) of these rejection notices?  Then I
> can take a look at the logs or at least try to come up with an idea of
> what's going on.
> 
> The mailing list is set up to munge email addresses with DMARC, but if
> you don't have DMARC set up then I'm not sure why you'd even get DKIM
> backflow -- unless you're signalling in DKIM, somehow, to block the
> messages.  But I'm not sure how you would signal that purely in DKIM.
> 
> For what it's worth, I have DKIM set up on my address (not this one) and
> when I send to the gnucash lists I do not receive any blowback.
> 
> If you look at https://bugs.launchpad.net/mailman/+bug/557493 you'll see
> that DKIM headers should not be stripped out.  On the other hand,
> currently, the list server is NOT set up to (re-)sign outgoing
> messages.  This is certainly something on the To Do list to fix, but
> requires lots of moving parts to get set up.

*Some* of the E-Mail providers out there are getting picky WRT DMARC/DKIM.  It 
seems like getting DMARC/DKIM *fully* set up on the outbound SMTP server used 
by Gnucash's Mailman list might be getting more urgent on the To Do list...

> 
> >> Mark
> 
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> 
> -derek
> 

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
 
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] [GNC-dev] Bugs.gnucash.org Up and Running

[Geert Janssens]

Op vrijdag 6 juli 2018 18:14:08 CEST schreef Derek Atkins:
> On Fri, July 6, 2018 11:59 am, John Ralls wrote:
> >> I suspect I could write a script using the Perl interface that would
> >> search for any references like this, and possibly hand-modify the SQL
> >> tables that need adjusting.   If nothing else I can look for any comment
> >> references to bugzilla.gnome.org  or a bug#
> >> that's not in the database.
> >> 
> >> Actually, I can probably do that in the json!  So there are 361 bugs
> >> that
> >> have a reference to "show_bug.cgi".  Only 287 of those reference
> >> bugzilla.gnome.org/show_bug.cgi
> >> .
> >> 
> >> Searching for "Bug # xxx" which wasn't imported is going to be harder.
> >> 
> >> I'm not sure what to change the bugzilla.gnome.org
> >>  references to...
> > 
> > I assume that you mean you don’t know what to change bugzilla.gnome.org
> >  references to when they refer to a bug that
> > we didn’t import to bugs.gnucash.org . I suppose
> > that there are two alternatives: We can import those bugs too or just
> > leave the links as-is. I don’t think that we want to import them. (The
> > third alternative, find their gitlab instances, will likely apply only to
> > a very few of them: Only open bugs being actively worked on or identified
> > as still a serious problem were migrated.)
> 
> Yes.
> 
> I can easily change local references.
> 
> I don't know how to modify references to bugs we didn't import.
> 
Depends on how much effort we're willing to spend.

You can query the db for all variations of bug #, bug  and 
bugzilla.gnome.org/show_bug.cgi.

The first two formats when referring to gnucash bugs can be left as they are. 
The third format when referring to gnucash bugs can be rewritten to
bug #

If the bugs don't refer to a gnucash bug you could try to find a 
gitlab.ngome.org url in the last few comments on the bug on bugzilla.gnome.org 
and substitute that in our comments. If no gitlab.gnome.org url is found in 
the bug, just replace it with the bugzilla.gnome.org url. There's not 
alternative in that case (this last option is needed for the first two 
formats, as our bug db doesn't have these bugs).

Geert


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] [GNC-dev] Bugs.gnucash.org Up and Running

[Derek Atkins]

On Fri, July 6, 2018 11:59 am, John Ralls wrote:
>
>> I suspect I could write a script using the Perl interface that would
>> search for any references like this, and possibly hand-modify the SQL
>> tables that need adjusting.   If nothing else I can look for any comment
>> references to bugzilla.gnome.org  or a bug#
>> that's not in the database.
>>
>> Actually, I can probably do that in the json!  So there are 361 bugs
>> that
>> have a reference to "show_bug.cgi".  Only 287 of those reference
>> bugzilla.gnome.org/show_bug.cgi
>> .
>>
>> Searching for "Bug # xxx" which wasn't imported is going to be harder.
>>
>> I'm not sure what to change the bugzilla.gnome.org
>>  references to...
>
> I assume that you mean you don’t know what to change bugzilla.gnome.org
>  references to when they refer to a bug that
> we didn’t import to bugs.gnucash.org . I suppose
> that there are two alternatives: We can import those bugs too or just
> leave the links as-is. I don’t think that we want to import them. (The
> third alternative, find their gitlab instances, will likely apply only to
> a very few of them: Only open bugs being actively worked on or identified
> as still a serious problem were migrated.)

Yes.

I can easily change local references.

I don't know how to modify references to bugs we didn't import.

> It’s worth noting that Gnome missed their date for shutting down new bugs,
> too. https://bugzilla.gnome.org/enter_bug.cgi?classification=__all
>  still
> lists *lots* of projects.

Interesting..

> Regards,
> John Ralls

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] [GNC-dev] Bugs.gnucash.org Up and Running

[John Ralls]

> On Jul 6, 2018, at 8:30 AM, Derek Atkins  wrote:
> 
> John,
> 
> On Fri, July 6, 2018 10:43 am, John Ralls wrote:
>> 
>> 
>>> On Jul 6, 2018, at 6:49 AM, Derek Atkins  wrote:
>>> 
>>> Richard,
>>> 
>>> Richard Ullger  writes:
>>> 
 John,
 
 Some links are pointing back to gnome bugzilla.
 
 See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665
>>> 
>>> The reason for this is that the commentor (YOU!) explicity put in the
>>> URL instead of using the appropriate shorthand "Bug #796665".
>>> 
>>> At this point I know of no way to fix this.
>>> 
>> 
>> That said, references to non-gnucash bugs using the shorthand will
>> probably get a bad URL because we didn’t copy all of Gnome’s database.
>> There’s no reasonable way to fix that either.
>> 
>> That’s also unlikely to be the only kind of stale URLs in the bug
>> database. The internet has changed a lot over the last 17 years (the
>> oldest bug, 58566, was opened 2001-08-05).
> 
> I suspect I could write a script using the Perl interface that would
> search for any references like this, and possibly hand-modify the SQL
> tables that need adjusting.   If nothing else I can look for any comment
> references to bugzilla.gnome.org  or a bug# 
> that's not in the database.
> 
> Actually, I can probably do that in the json!  So there are 361 bugs that
> have a reference to "show_bug.cgi".  Only 287 of those reference
> bugzilla.gnome.org/show_bug.cgi .
> 
> Searching for "Bug # xxx" which wasn't imported is going to be harder.
> 
> I'm not sure what to change the bugzilla.gnome.org 
>  references to...

I assume that you mean you don’t know what to change bugzilla.gnome.org 
 references to when they refer to a bug that we 
didn’t import to bugs.gnucash.org . I suppose that 
there are two alternatives: We can import those bugs too or just leave the 
links as-is. I don’t think that we want to import them. (The third alternative, 
find their gitlab instances, will likely apply only to a very few of them: Only 
open bugs being actively worked on or identified as still a serious problem 
were migrated.)

It’s worth noting that Gnome missed their date for shutting down new bugs, too. 
https://bugzilla.gnome.org/enter_bug.cgi?classification=__all 
 still lists 
*lots* of projects.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] [GNC-dev] Bugs.gnucash.org Up and Running

[John Ralls]

> On Jul 6, 2018, at 6:49 AM, Derek Atkins  wrote:
> 
> Richard,
> 
> Richard Ullger  writes:
> 
>> John,
>> 
>> Some links are pointing back to gnome bugzilla.
>> 
>> See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665
> 
> The reason for this is that the commentor (YOU!) explicity put in the
> URL instead of using the appropriate shorthand "Bug #796665".
> 
> At this point I know of no way to fix this.
> 

That said, references to non-gnucash bugs using the shorthand will probably get 
a bad URL because we didn’t copy all of Gnome’s database. There’s no reasonable 
way to fix that either.

That’s also unlikely to be the only kind of stale URLs in the bug database. The 
internet has changed a lot over the last 17 years (the oldest bug, 58566, was 
opened 2001-08-05).

Regards,
John Ralls


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] [GNC-dev] Bugs.gnucash.org Up and Running

[Derek Atkins]

Richard,

Richard Ullger  writes:

> John,
>
> Some links are pointing back to gnome bugzilla.
>
> See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665

The reason for this is that the commentor (YOU!) explicity put in the
URL instead of using the appropriate shorthand "Bug #796665".

At this point I know of no way to fix this.

> I assume Gnucash bugs in gnome bugzilla will disappear at some point.

It's unclear what will happen.  I was under the impression that it would
remain in read-only mode for a while, but it's possible it may
disappear.

> Regards,
>
> Richard

> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

[GNC] GNC List and DKIM (was Re: how to share style sheets between computers in GnuCash 3.1?)

[Derek Atkins]

Hi Mark,

Geert Janssens  writes:

>> BTW I get a lot of DKIM rejection reports from recipient servers when I
>> send mail to the list.  Is that because the list server strips the
>> anti-spam headers from my message before it forwards it out?  Maybe there
>> is a patch for that.
>> 
> I don't know. This is something our mailing list adminstrator may know more 
> about... Forwarding back to the list...

Could you forward me one (or more) of these rejection notices?  Then I
can take a look at the logs or at least try to come up with an idea of
what's going on.

The mailing list is set up to munge email addresses with DMARC, but if
you don't have DMARC set up then I'm not sure why you'd even get DKIM
backflow -- unless you're signalling in DKIM, somehow, to block the
messages.  But I'm not sure how you would signal that purely in DKIM.

For what it's worth, I have DKIM set up on my address (not this one) and
when I send to the gnucash lists I do not receive any blowback.

If you look at https://bugs.launchpad.net/mailman/+bug/557493 you'll see
that DKIM headers should not be stripped out.  On the other hand,
currently, the list server is NOT set up to (re-)sign outgoing
messages.  This is certainly something on the To Do list to fix, but
requires lots of moving parts to get set up.

>> Mark

> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] [GNC-dev] Bugs.gnucash.org Up and Running

[Richard Ullger]

On Fri, 29 Jun 2018, 23:13 John Ralls,  wrote:

> We've completed the migration of Bugzilla to https://bugs.gnucash.org and
> we're ready to resume normal bug ops there. The updates on
> bugzilla.gnome.org are still running (after 2 hours not quite halfway
> done), but that doesn't affect using https://bugs.gnucash.org.
>
> There's one change since yesterday's announcement: We've shortened the
> pseudo-addresses for bugmail:
>
> Group Elements
> c...@gnucash.bugs Backend-SQL, Backend-XML, Budgets, Build
> System,
>   Business, Currency and Commodity, Engine,
> Python
>   Bindings, Scheduled Transactions
> documentat...@gnucash.bugsDocumentation, Translations, Website
> gene...@gnucash.bugs  General
> imp...@gnome.bugs Import-AqBanking, Import-CSV, Import-OFX,
> Import-
>   Other, Import-QIF, Import-QSF, TXF Export
> ma...@gnucash.bugsMacOS
> repo...@gnucash.bugs  Check Printing, Reports
> u...@gnucash.bugs   Register, Regist-2, User Interface General
> wind...@gnucash.bugs  Windows
> all-b...@gnucash.bugs Everything
>
> For now we've adopted the Gnome skin for familiarity, but we'd love to
> have someone who's artistically inclined to design us a GnuCash-specific
> one!
>
> Regards,
> John Ralls
>

John,

Some links are pointing back to gnome bugzilla.

See comment 3 on https://bugs.gnucash.org/show_bug.cgi?id=796665

I assume Gnucash bugs in gnome bugzilla will disappear at some point.

Regards,

Richard
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Register issues within 3.2

[Richard Ullger]

On Fri, 6 Jul 2018, 03:50 Alun Champion,  wrote:

> OS: MacOS
> Version: Gnucash 3.2
>
> After pasting (Cmd-V) data into a register the register will no longer
> receive normal keyboard input, just the annoying keyboard beep.
>
> Enter still works, as does tab but no data entry from the keyboard in any
> field in the register for that account. Other registers for other accounts
> continue to receive input (unless you paste something into that register).
>
> This is very annoying because I often paste data from online account data.
>-Alun.
>

https://bugs.gnucash.org/show_bug.cgi?id=796665
https://bugs.gnucash.org/show_bug.cgi?id=795731

Fixed in git
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.