Re: Do Groff letter modes work in latest git?

[Myles English <mylesenglish@gmail.com>]

Luis Anaya writes:

> Myles English <mylesenglish@gmail.com> writes:
>
>> Thanks for checking but did you start with emacs -Q ?
>
> I tried with emacs -Q. I loaded the following from *scratch*
>
> #+begin_src emacs-lisp
>
> (add-to-list 'load-path "/sdcard-ext/org-mode/lisp")
> (add-to-list 'load-path "/sdcard-ext/org-mode/contrib/lisp")
> (require 'org-install)
> (require 'org)
> (require 'org-e-groff)
>
> #+end_src
>
>
>> I tried it and I don't get a letter.  I get the attached screenshot.  Is
>> that what you get too?
>
> No, certainly not. This is the resultant PDF and Groff files.
>

Did you mean to attach your Groff file?  Here's mine anyway:

.AF "Org User" 
.TL
Example from Worg
.AU "Mickey Mouse"
.ND "2012-08-19"
.H 1 "FROM \fC:FROM:\fP "
.P
Joe Smith
00 Street
City, ST, 00000

.H 1 "TO \fC:TO:\fP "
.P
Maria Rivera
Urbanizacion Palma Lejos
Calle 22, Bloque A, Numero 10
Ciudad, ES, 00000

.H 1 "BODY \fC:BODY:\fP "
.P
letter content

.H 1 "Copy to \fC:NS:\fP "
.P
Jill Brown


I am wondering if semiblock should be in org-e-groff-classes?  Says on
Worg that "The [#+GROFF_CLASS:] must be listed in org-e-groff-classes"
but here is the org-e-groff-classes from org-e-groff.el:

(("file" ".MT 1"
  (:heading 'default :type "memo" :last-section "toc"))
 ("internal" ".MT 0"
  (:heading 'default :type "memo" :last-section "toc"))
 ("programmer" ".MT 2"
  (:heading 'default :type "memo" :last-section "toc"))
 ("engineer" ".MT 3"
  (:heading 'default :type "memo" :last-section "toc"))
 ("external" ".MT 4"
  (:heading 'default :type "memo" :last-section "toc"))
 ("letter" ".MT 5"
  (:heading 'default :type "memo" :last-section "sign"))
 ("custom" ".so file"
  (:heading custom-function :type "custom" :last-section "toc"))
 ("dummy" ""
  (:heading 'default :type "memo"))
 ("ms" "ms"
  (:heading 'default :type "cover" :last-section "toc"))
 ("se_ms" "se_ms"
  (:heading 'default :type "cover" :last-section "toc"))
 ("none" ""
  '(:heading 'default :type "custom")))

I don't know what else to try after this, any suggestions?

Myles