public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Eamon Byrne <vote1nbn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Cannot find reference.docx
Date: Thu, 3 May 2018 14:49:33 -0700 (PDT)	[thread overview]
Message-ID: <ee2ad8ce-8c57-4bab-9154-a9fa50d5417f@googlegroups.com> (raw)
In-Reply-To: <2a803abf-c105-4c3b-94b6-9ef05c90cbfe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]

Many thanks for clarifying. 

On Thursday, May 3, 2018 at 10:17:34 AM UTC+10, Eamon Byrne wrote:
>
> Hi. Your amazing program is working fine, and now I'm moving on to 
> fine-tuning.
>
> In the docs, it says that for Windows installs,  there is a "Default user 
> data directory" at   C:\users\username\AppData\Roaming\pandoc
>
> Indeed, typing "pandoc --version" at the command prompt tells me that is 
> so.
>
> However, there is no such folder in ..\Roaming  (Unless it's a hidden 
> folder?)
>
> I was presuming that a default reference.docx file came with the pandoc 
> installation, and would be there. I can't find this file anywhere on my 
> computer.
>
> Do I have to create a new pandoc folder under  
> C:\users\username\AppData\Roaming\   and place my own reference.docx file 
> into it?
>
> Or was my install using the msi unsuccessful and I should reinstall pandoc.
>
>  Other than that, all good.
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ee2ad8ce-8c57-4bab-9154-a9fa50d5417f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2237 bytes --]

      parent reply	other threads:[~2018-05-03 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  0:17 Eamon Byrne
     [not found] ` <2a803abf-c105-4c3b-94b6-9ef05c90cbfe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-05-03  1:14   ` Ivan Lazar Miljenovic
     [not found]     ` <CA+u6gbxGSuFUdc3thWZDvFhW6XDxxa0Xy=wr+eHhhvaFMF7x-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-05-03 16:31       ` John MacFarlane
2018-05-03 16:28   ` John MacFarlane
2018-05-03 21:49   ` Eamon Byrne [this message]

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

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

  git send-email \
    --in-reply-to=ee2ad8ce-8c57-4bab-9154-a9fa50d5417f@googlegroups.com \
    --to=vote1nbn-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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.
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 NNTP newsgroup(s).