Byte order mark always make some files modified
Hi, Following files are always marked as modified in my repos when swtich between maint and master back and forth, sometimes these modified files prevent git from git-checkout, meanwhile they cannot be stashed or checked out with `checkout --`. modified: doc/README-de.win32-bin.txt modified: doc/README-fr.win32-bin.txt modified: doc/README-it.win32-bin.txt modified: doc/README-nl.win32-bin.txt modified: doc/README-zh_CN.win32-bin.txt modified: doc/README-zh_TW.win32-bin.txt modified: doc/README.win32-bin.txt modified: doc/examples/downloaded.mt940 I searched archived mails in gnucash-devel, set `git config --global core.autocrlf input`. However, this only affects the first time when checkout branch from master to maint. Above issue happens again when checkout back to master from maint. Really confused, have no idea why this happens and not sure whether it's an CRLF-related issue. -- Regards, Chenxiong Qi ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Byte order mark always make some files modified
> On Dec 27, 2014, at 3:50 AM, Chenxiong Qi wrote: > > Hi, > > Following files are always marked as modified in my repos when swtich > between maint and master back and forth, sometimes these modified > files prevent git from git-checkout, meanwhile they cannot be stashed > or checked out with `checkout --`. > > modified: doc/README-de.win32-bin.txt > modified: doc/README-fr.win32-bin.txt > modified: doc/README-it.win32-bin.txt > modified: doc/README-nl.win32-bin.txt > modified: doc/README-zh_CN.win32-bin.txt > modified: doc/README-zh_TW.win32-bin.txt > modified: doc/README.win32-bin.txt > modified: doc/examples/downloaded.mt940 > > I searched archived mails in gnucash-devel, set `git config --global > core.autocrlf input`. However, this only affects the first time when > checkout branch from master to maint. Above issue happens again when > checkout back to master from maint. Really confused, have no idea why > this happens and not sure whether it's an CRLF-related issue. Those files' line endings are supposed to be controlled by .gitattributes, which overrides the core.autocrlf setting. I tweaked the globs in .gitattributes 2 Dec., and Mike Alexander removed the line endings from the repo on the 8th. This worked correctly for me just now, with no core.autocrlf setting. Did you experience the problem with a fresh checkout or an older one? README.win32-bin.txt and downloaded.mt940 don't have BOMs. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: git always make some files modified
Am Samstag, 27. Dezember 2014, 09:22:12 schrieb John Ralls: > > Following files are always marked as modified in my repos when swtich > > between maint and master back and forth, sometimes these modified > > files prevent git from git-checkout, meanwhile they cannot be stashed > > or checked out with `checkout --`. > > > > modified: doc/README-de.win32-bin.txt > > modified: doc/README-fr.win32-bin.txt > > modified: doc/README-it.win32-bin.txt > > modified: doc/README-nl.win32-bin.txt > > modified: doc/README-zh_CN.win32-bin.txt > > modified: doc/README-zh_TW.win32-bin.txt > > modified: doc/README.win32-bin.txt > > modified: doc/examples/downloaded.mt940 > > > > I searched archived mails in gnucash-devel, set `git config --global > > core.autocrlf input`. However, this only affects the first time when > > checkout branch from master to maint. Above issue happens again when > > checkout back to master from maint. Really confused, have no idea why > > this happens and not sure whether it's an CRLF-related issue. > > Those files' line endings are supposed to be controlled by .gitattributes, > which overrides the core.autocrlf setting. Yes, the .gitattributes file is the other source of CRLF-related settings. I think 1-2 years ago it took me a while to discover how to get rid of this same "modified: doc/README...txt" message. I got stuck in those message when switching between master and some older branch such as maint or even older. My solution is as follows: - Remove the .gitattributes file - Commit this removal into git (which makes the modified-message go away), - And reset the master branch back to the original master. It still sounds a bit funny to me, but this somehow works to get rid of those error message. > README.win32-bin.txt and downloaded.mt940 don't have BOMs. Yes, byte order mark (BOM) is the wrong keyword here - we are only talking about line endings, not byte order. Regards, Christian ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Byte order mark always make some files modified
--On December 27, 2014 at 9:22:12 AM -0800 John Ralls wrote: On Dec 27, 2014, at 3:50 AM, Chenxiong Qi wrote: Hi, Following files are always marked as modified in my repos when swtich between maint and master back and forth, sometimes these modified files prevent git from git-checkout, meanwhile they cannot be stashed or checked out with `checkout --`. modified: doc/README-de.win32-bin.txt modified: doc/README-fr.win32-bin.txt modified: doc/README-it.win32-bin.txt modified: doc/README-nl.win32-bin.txt modified: doc/README-zh_CN.win32-bin.txt modified: doc/README-zh_TW.win32-bin.txt modified: doc/README.win32-bin.txt modified: doc/examples/downloaded.mt940 I searched archived mails in gnucash-devel, set `git config --global core.autocrlf input`. However, this only affects the first time when checkout branch from master to maint. Above issue happens again when checkout back to master from maint. Really confused, have no idea why this happens and not sure whether it's an CRLF-related issue. Those files' line endings are supposed to be controlled by .gitattributes, which overrides the core.autocrlf setting. I tweaked the globs in .gitattributes 2 Dec., and Mike Alexander removed the line endings from the repo on the 8th. This worked correctly for me just now, with no core.autocrlf setting. Did you experience the problem with a fresh checkout or an older one? README.win32-bin.txt and downloaded.mt940 don't have BOMs. And what sort of machine is this on? Windows, Mac, or Linux? I have core.autocrlf set to "input" and it seems to work ok for me on my Mac. You might want to reread the section on "End-of-line conversion" in the "git help attributes" man page. Mike ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: git always make some files modified
--On December 27, 2014 at 9:16:56 PM +0100 Christian Stimming wrote: My solution is as follows: - Remove the .gitattributes file - Commit this removal into git (which makes the modified-message go away), - And reset the master branch back to the original master. Removing .gitattributes is a very bad idea. It will mess up the line endings in your repository. It will only affect you if you don't push things to other repositories, but it is still not a good idea. Anyone who pushes things to other repositories should not remove that file (or change it unless they are very careful). Git repositories are supposed to have all text files normalized to LF line endings. Then autocrlf controls what happens to them in your checked out copy. One of the big problems is determining what files are text files and so should be normalized. If you remove .gitattributes then you will cause git to misidentify text files and mess up line endings in things you commit to the repository. This is particularly true on Windows machines, but can be a problem on Linux machines or Macs too. Mike ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: make fails
Well, I learned a lot more than I ever thought trying to figure this out, but in the end I am embarrassed with the problem.. I was setting the prefix in my configure command, and while I did delete the source and start from scratch--the installation directory had files in it, not sure how as I never got to make install, but either way I was behind the keyboard, and the variety of errors came from head on collisions. Changing the installation directory brought everything to normal.. Thanks, Bob > On Dec 24, 2014, at 10:52 PM, John Ralls wrote: > > >> On Dec 24, 2014, at 6:12 PM, GnuCash wrote: >> >> Not sure if this should be under the other emails, but I'm unable to get >> this to work for the last little bit, the error is similar. I've tried >> to use "git clean -fdx" and then even wiped it all and started again, >> but still having the same error.. >> - >> gnc-int128.hpp:229:41: error: 'UINT64_MAX' was not declared in this >> scope >> gnc-int128.hpp:229:53: error: 'UINT64_MAX' was not declared in this >> scope > > C++11 is required for master. Either your compiler is too old and is lying to > configure about its C++11 status or you have a defective stdint.h. Even if > you manage to solve this problem it's likely that you'll have more as the C++ > rewrite proceeds. > > We are deliberately pushing the envelope on compiler capability here in order > to use the new language features; not all current stable distros are going to > be able to build master, never mind even slightly obsolete ones. Sorry. > > Regards, > John Ralls > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Report wrapper to call python scripts?
Just a thought regarding the need for a python distribution for the python binding on Windows/OS X, would it be an option to build a single executable with the gnucash bindings (see http://www.orbitals.com/programs/pyexe.html or http://www.decalage.info/en/python/py2exe) ? This would give a complete control on the required python version/package distribution. And if the user is more knowledgeable re python, it could go with its own distribution (+ other relevant comment in this thread) ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
