January 2013 Archives by thread
Starting: Wed Jan 2 14:35:50 EST 2013
Ending: Thu Jan 31 16:52:57 EST 2013
Messages: 206
- Someone is attempting to sell GnuCash.
Geoff Hilton
- user.config file and path
Derek Atkins
- Gnucash for ChromeOS
Derek Atkins
- requesting a feature
سید علی اکبر نجفیان
- GnuCash for Android with double entry accounting
Ngewi Fet
- Unstable Download
John Ralls
- GnuCash download stats
Cristian Marchi
- r22691 - htdocs/branches/beta - Revert "Separate unstable download information to a separate file, make"
Geert Janssens
- Testing docs in development version
Yawar Amin
- Migrating gnucash website from svn to git
Geert Janssens
- [Bug 638955] "Close Books" needs documentation
Yawar Amin
- [gnucash-htdocs] Change GnuCash website `Mailing Lists' link name
Yawar Amin
- [PATCH] Free memory in the gnc_gnome_help function
Yawar Amin
- Git Migration: github with svn access
Yawar Amin
- Bug 691762: behaviour of Find dialog box's `Reconcile' criteria buttons
Yawar Amin
- Longer term projects
Geert Janssens
- Making GnuCash development on Windows easier, one step at the time
Geert Janssens
- Backport policy regarding new strings ?
Geert Janssens
- r22681 - gnucash/trunk/src - Implement a Book Option to give users the choice to use the transaction number field (default and current behaviour) or, alternatively, the split action field of the anchor split for 'Num' column on registers, reports, import and export, where applicable. The difference between the two is that with the default, the same 'Num' is displayed for a given transaction regardless of what register it is viewed in and with the new option, a different 'Num' can be entered/displayed for a given transaction in each register it is viewed in. In both cases, the 'next number logic' of the 'Num' cell is based on the account of the register the transaction is entered/viewed from but in one case it fills the transaction number, in the other, it fills the split action field of the anchor split (with the transaction number field displayed in the register cell labeled 'T-Num'). In both cases, both fields are visible and can be used as free-form text in double-line mode for any value the user wants. If the new option is not selected, there should be no change in Gnucash's behaviour with the exception of displaying the book options dialog in 'new book' situations.
Geert Janssens
- r22681 - gnucash/trunk/src - Implement a Book Option to give users the choice to use the transaction number field (default and current behaviour) or, alternatively, the split action field of the anchor split for 'Num' column on registers, reports, import and export, where applicable. The difference between the two is that with the default, the same 'Num' is displayed for a given transaction regardless of what register it is viewed in and with the new option, a different 'Num' can be entered/displayed for a given transaction in each register it is viewed in. In both cases, the 'next number logic' of the 'Num' cell is based on the account of the register the transaction is entered/viewed from but in one case it fills the transaction number, in the other, it fills the split action field of the anchor split (with the transaction number field displayed in the register cell labeled 'T-Num'). In both cases, both fields are visible and can be used as free-form text in double-line mode fo
Alex Aycinena
- r22681 - gnucash/trunk/src - Implement a Book Option to give users the choice to use the transaction number field (default and current behaviour) or, alternatively, the split action field of the anchor split for 'Num' column on registers, reports, import and export, where applicable. The difference between the two is that with the default, the same 'Num' is displayed for a given transaction regardless of what register it is viewed in and with the new option, a different 'Num' can be entered/displayed for a given transaction in each register it is viewed in. In both cases, the 'next number logic' of the 'Num' cell is based on the account of the register the transaction is entered/viewed from but in one case it fills the transaction number, in the other, it fills the split action field of the anchor split (with the transaction number field displayed in the register cell labeled 'T-Num'). In both cases, both fields are visible and can be used as free-form text in double-line mode fo
Alex Aycinena
- My Curiosity is Piqued: svn.gnucash Directory Restructuring
David T.
- Issue running git-svn-mirror script on code
Derek Atkins
- Lot transfers
Peter Dey
- How does GnuCash import OFX double entry transactions?
Ngewi Fet
- Gnucash is going to be featured on the SourceForge front page
Christian Stimming
- Github Repositories Will Be Regenerated Next Week
John Ralls
- I would like to help translating Gnucash help manual
Zong Han Xie
- GnuCash for Android banner in homepage
Cristian Marchi
- make check failure: missing POTFILES
Larry Evans
- GSOC
John Ralls
- Permission to use the icon
Evgeny
- Notification mails for git repos
Geert Janssens
- Github reset
Geert Janssens
Last message date:
Thu Jan 31 16:52:57 EST 2013
Archived on: Thu Jan 31 16:53:06 EST 2013
This archive was generated by
Pipermail 0.09 (Mailman edition).