After homing X and Y, can I auto move to a non 0,0 location?

I've recently gotten switch-based homing working on my 12"x12" DIY xyz mill.  The mill is the style where the spindle is stationary, and the bed moves in two directions underneath.  (I'm sure there's a name for that.)

0,0 is at the near left corner of the bed (of course), and after homing, with the spindle above that point, the bed is basically as far from me as possible.

I'd prefer it to home to 12,12 instead of 0,0, which would leave the bed as close to me as possible.  I've tried homing against the upper limits instead of the lower limits, with a HOME_OFFSET of 12, thinking that would help, but after homing at the near corner, the mill once again moves all the way to the other end, in order to end up at 0,0.

Is there a way to accomplish what I want?  If I can't convince it to actually home to the near corner, is there a way to automatically invoke an arbitrary move after homing?  

Post your INI file please and we'll see what needs editing.

And yes, homing is a never-ending struggle for LCNC users - both new and old-but-rusty.

Also make sure you read this entire document:

linuxcnc.org/docs/html/config/ini-homing.html#_home

It seems like HOME is the INI variable you need to change.

Thank you both. I'm certain you're right: Home is set to 0. So if I switch to homing at the 12,12 corner, and change HOME to 12 for both X and Y, it will almost certainly do what I want. INI file attached, in any case.   If HOME had been grouped with the other HOME_* variables, I might have noticed. 

I also need to stop using google to find linuxcnc docs, rather than having some known-good bookmarks on hand. Not only does google often point to old versions of the docs, it will also take you into the middle of the document. While I'd read most of the page @PCW linked to, I think I'd never even seen the first several sections, with the excellent colorful diagrams. Wish I had!

Ahh you see the light! Be sure to read the correct version of the documents for the version you are using. Everything you need to know is there in those docs!