emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: torys.anderson@gmail.com (Tory S. Anderson)
To: John Hendy <jw.hendy@gmail.com>
Cc: Andreas Kiermeier <andreas.kiermeier@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: CV in orgmode for export to pdf (and html?)
Date: Fri, 19 Sep 2014 13:15:46 -0400	[thread overview]
Message-ID: <87bnqbmszh.fsf@gmail.com> (raw)
In-Reply-To: <CA+M2ft9W2QCZUSaQ+7XM4EZ7zxz5bEp4nQ2kykqWrx1v0KVggg@mail.gmail.com> (John Hendy's message of "Fri, 19 Sep 2014 10:06:39 -0500")

Very nice, John. Thanks for sharing the LaTeX! 

John Hendy <jw.hendy@gmail.com> writes:

> Like the rest, I picked straight LaTeX, as it just felt like forcing Org to
> do something unnatural, in my opinion. At least, if you get into any sort
> of formatting stuff, it just didn't feel right. Here's some other mailing
> list discussions if you haven't run into them:
> - https://www.mail-archive.com/emacs-orgmode@gnu.org/msg37000.html
> - http://web.archiveorange.com/archive/v/Fv8aAUnm6O4rHfVY6k0p
>
> And a github repo:
> - https://github.com/fasheng/fsh-orgmode-latex-cv
>
> I still have a bookmarks folder in Chromium from when I was hunting around.
> Here are the ones that, apparently, I found worth to make the Ctrl+D cut
> for future reference if you're interested
> -
> http://linux.dsplabs.com.au/resume-writing-example-latex-template-linux-curriculum-vitae-professional-cv-layout-format-text-p54/
> - http://www.latextemplates.com/templates/curriculum_vitaes/6/cv_6.tex
> - http://jblevins.org/projects/cv-template/
> - http://nitens.org/taraborelli/cvtex
>
> I haven't updated mine since 2011, when I updated it for my current job. I
> went with an internal CV so that I could list accomplishments that would be
> considered confidential (patent applications, internal reports, etc.). I
> did create a dummy version, which I've attached (tex/pdf). Re-looking at
> it, I can't decide if I still like it or not. At the time, I was really
> happy with it as my first LaTeX CV :) I'd also probably consider it a
> hybrid CV/resume -- I liked describe some of my previous job
> responsibilities, while including papers/presentations/etc.
>
>
> Good luck!
> John
>
>
> On Fri, Sep 19, 2014 at 5:29 AM, Andreas Kiermeier <
> andreas.kiermeier@gmail.com> wrote:
>
>> Hi Rainer,
>>
>> like Tory I prepare my CV using latex directly. I've been using
>> "moderncv" for several years now and have been quite happy with it
>> (though that was before I've started using org). But even now, I can't
>> see how using org, would add to what I already have.
>>
>> Mind you, I tend to add to my CV (mainly publications and experience)
>> and revise it when needed, rather than adapt it to different
>> situations.
>>
>> Cheers,
>>
>> Andreas
>>
>>
>>
>> On 19 September 2014 19:40, Tory S. Anderson <torys.anderson@gmail.com>
>> wrote:
>> > I do mine in LaTeX and haven't had a reason to change that. I keep a
>> "Master" CV/resumé with all the gratuitous information in all categories,
>> then make subdirs for each submission and the trimmed-down versions of my
>> resume that I sent out. At this stage in my career–where I am still
>> tailoring resumés to employers and not really keeping a no-holds-barred CV—
>> this is the best workflow I've found. I'm not sure how I'd go about
>> versioning, trimming, and tracking things as neatly in an all-org
>> environment.
>> >
>> > I'm presuming you just want a full-disclosure CV, though? Org makes more
>> sense there.
>> >
>> > Rainer M Krug <Rainer@krugs.de> writes:
>> >
>> >> Hi
>> >>
>> >> I am looking for examples / templates for CVs written using org, as I
>> >> decided to ose org for my CV.
>>
>>

  reply	other threads:[~2014-09-19 17:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19  9:18 CV in orgmode for export to pdf (and html?) Rainer M Krug
2014-09-19 10:10 ` Tory S. Anderson
2014-09-19 10:29   ` Andreas Kiermeier
2014-09-19 15:06     ` John Hendy
2014-09-19 17:15       ` Tory S. Anderson [this message]
2014-09-22  8:24         ` Rainer M Krug
2014-10-29 19:35   ` Karl Voit
2014-09-19 15:38 ` Dan Griswold
2014-09-19 19:52 ` Brady Trainor
2014-09-19 20:18   ` Nicolas Goaziou
2014-09-19 23:01     ` Rasmus
2014-09-22  8:30       ` Rainer M Krug
2014-09-21 19:59     ` Myles English
2014-09-22  8:31       ` Rainer M Krug
2014-09-22 21:37       ` Myles English
2014-09-23  6:56         ` Rainer M Krug
2014-09-22  8:28   ` Rainer M Krug
2014-09-20  0:49 ` Dan Griswold
2014-09-20  5:56   ` Vikas Rawal
2014-09-22  8:32     ` Rainer M Krug
2014-09-20  6:36   ` Joseph Vidal-Rosset
2014-09-22  8:32     ` Rainer M Krug
2014-09-22  8:23   ` CV in orgmode for export to pdf (and html? Rainer M Krug
2014-09-22 11:55     ` Nick Dokos
2014-09-23  9:06     ` Rasmus
     [not found]     ` <87fvfihfh8.fsf@gmx.us>
2014-09-23  9:24       ` Rainer M Krug
2014-09-20  7:45 ` CV in orgmode for export to pdf (and html?) Xavier Garrido
2014-09-22  8:33   ` Rainer M Krug

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bnqbmszh.fsf@gmail.com \
    --to=torys.anderson@gmail.com \
    --cc=andreas.kiermeier@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).