Off Topic > Off Topic
Programming Megathread
<< < (78/241) > >>
ZSNO:

--- Quote from: Foxscotch on January 26, 2016, 03:52:31 PM ---um, plenty of people still use emacs and vim
even for people who don't, preferring the command line to a gui file browser isn't uncommon

--- End quote ---
Are you implying vim and emacs are restricted to 80 width? Because they're not.
Foxscotch:

--- Quote from: ZSNO on January 26, 2016, 04:09:44 PM ---Are you implying vim and emacs are restricted to 80 width? Because they're not.

--- End quote ---
they are used from the command line... which is by default 80 columns wide
the only time they'd ever need to change it is someone not following decent style conventions
ZSNO:

--- Quote from: Foxscotch on January 26, 2016, 05:00:29 PM ---they are used from the command line... which is by default 80 columns wide
the only time they'd ever need to change it is someone not following decent style conventions

--- End quote ---
What "default" are you using? Barebones linux distros scale properly to the monitor. Providing more than 80 char width for not terribly old monitors
Foxscotch:

--- Quote from: ZSNO on January 26, 2016, 05:10:52 PM ---What "default" are you using? Barebones linux distros scale properly to the monitor. Providing more than 80 char width for not terribly old monitors

--- End quote ---
I mean like this

Headcrab Zombie:

--- Quote from: Headcrab Zombie on January 26, 2016, 09:31:20 AM ---loving QuickBooks Online API
Whoever wrote this stuff doesn't have enough English skills to give descriptive error messages that makes sense
"Can not instanti specified is unsupported or invalid"
pls

--- End quote ---
God damn
So the problem was that I had to specify the invoice's tax details.
Even though I was updating an existing invoice with tax details already specified, and I was using a "sparse" update, which according to Intuit's API documentation, is supposed to only update the fields I specify, and leave everything else alone.
But really though, is one thing to make a mistake, but none of this would be a problem if they could write sensible, descriptive error messages with understandable English
Navigation
Message Index
Next page
Previous page

Go to full version