Re: 2.3.15.1 OS X: new file not properly bound

2010-08-31 Thread John Ralls
On Aug 24, 2010, at 4:08 PM, John Ralls wrote: On Aug 24, 2010, at 9:45 AM, G.W.Pigman III wrote: If I try to enter a description that begins with the letter N, gnucash opens a new file. Next to new file in the file menu is N, not command-N, so I assume that new file is not properly

Re: 2.3.15.1 OS X: new file not properly bound

2010-08-31 Thread John Ralls
On Aug 31, 2010, at 3:44 PM, John Ralls wrote: On Aug 24, 2010, at 4:08 PM, John Ralls wrote: On Aug 24, 2010, at 9:45 AM, G.W.Pigman III wrote: If I try to enter a description that begins with the letter N, gnucash opens a new file. Next to new file in the file menu is N, not

Re: 2.3.15.1 OS X: new file not properly bound

2010-08-28 Thread Matthew MacLeod
If I try to enter a description that begins with the letter N, gnucash opens a new file. Next to new file in the file menu is N, not command-N, so I assume that new file is not properly bound. Darn. I thought I had that problem fixed. In the short term, try copying

Re: 2.3.15.1 OS X: new file not properly bound

2010-08-28 Thread John Ralls
On Aug 27, 2010, at 3:50 PM, Matthew MacLeod wrote: If I try to enter a description that begins with the letter N, gnucash opens a new file. Next to new file in the file menu is N, not command-N, so I assume that new file is not properly bound. Darn. I thought I had that problem fixed. In

2.3.15.1 OS X: new file not properly bound

2010-08-24 Thread G.W.Pigman III
If I try to enter a description that begins with the letter N, gnucash opens a new file. Next to new file in the file menu is N, not command-N, so I assume that new file is not properly bound. Mac Pigman ___ gnucash-devel mailing list

Re: 2.3.15.1 OS X: new file not properly bound

2010-08-24 Thread John Ralls
On Aug 24, 2010, at 9:45 AM, G.W.Pigman III wrote: If I try to enter a description that begins with the letter N, gnucash opens a new file. Next to new file in the file menu is N, not command-N, so I assume that new file is not properly bound. Darn. I thought I had that problem fixed.