John MacFarlane | 1 Feb 16:40 2011
Picon

pandoc 1.8.0.1 in macports!

I'm happy to announce that, after many years with a badly out-of-date pandoc
in MacPorts, we have a new maintainer (singingwolfboy) and an up-to-date
package.

John

Perry Wagle | 1 Feb 22:42 2011
Picon

Re: images and text

Here's the HTML to do it from way back (and still works):

<img align="left" src="perry-cropped.small.jpg">
<h2>
Perry Wagle
(<i>email:</i> <a href="mailto:wagle <at> xxx">wagle <at> xxx</a>)
</h2>
In September 2001, I joined 
<A HREF="http://yyy/">yyy</a>'s 
<A HREF="http://zzz/">zzz</a> research group
to work on foobarred Linux distributions.
... and so on...

The align="left" in the <img> seems to be the trick.

On Aug 18, 2010, at 7:36 AM, John MacFarlane wrote:

> +++ Perry Wagle [Aug 17 10 22:41 ]:
>>   One thing I left out was that back in the day, my website was of the form:
>> 
>>   XXX texttexttext
>>   XXX texttexttext
>>   texttexttexttext...
>>   texttexttexttext...
>> 
>>   where XXX was a picture
>> 
> 
> For this kind of thing you probably want to put the picture inside
> a <div>..</div> and use CSS.
(Continue reading)

Perry Wagle | 1 Feb 23:05 2011
Picon

Re: images and text

Ah, but according to http://www.w3.org/TR/html401/present/graphics.html, I'm doing deprecated
stuff, and so need to go off now and learn CSS: like you said.

-- Perry

On Feb 1, 2011, at 1:42 PM, Perry Wagle wrote:

> Here's the HTML to do it from way back (and still works):
> 
> <img align="left" src="perry-cropped.small.jpg">
> <h2>
> Perry Wagle
> (<i>email:</i> <a href="mailto:wagle <at> xxx">wagle <at> xxx</a>)
> </h2>
> In September 2001, I joined 
> <A HREF="http://yyy/">yyy</a>'s 
> <A HREF="http://zzz/">zzz</a> research group
> to work on foobarred Linux distributions.
> ... and so on...
> 
> The align="left" in the <img> seems to be the trick.
> 
> On Aug 18, 2010, at 7:36 AM, John MacFarlane wrote:
> 
>> +++ Perry Wagle [Aug 17 10 22:41 ]:
>>>  One thing I left out was that back in the day, my website was of the form:
>>> 
>>>  XXX texttexttext
>>>  XXX texttexttext
>>>  texttexttexttext...
(Continue reading)

Jesse Rosenthal | 3 Feb 00:37 2011

Re: paths to template files

Hello,

On Wednesday, January 27, 2010 4:53:59 AM UTC-5, Joost Kremers wrote:

A slightly different approach, but with more flexibility, might be to use profiles. These would be files somewhere under ~/.pandoc containing pandoc settings. Instead of specifying all settings on the command line each time you run pandoc, you'd then just say `pandoc --profile=<my_profile> <input_file>'.


Sorry to dig up an old thread, but I was wondering if this was officially decided against. I'd be happy to put something together to allow it -- I, at least, would find it *extremely* useful (I have a few very different LaTeX templates I use often) so I'd probably make the patches for myself anyway. I was thinking of just using the same format as in the configuration files for the Joost Kremer's pandoc emacs mode, unless there's any objection. And any options passed together with the profile would take precedence. (I imagine the opt would just be `--profile='.)

Anyway, as I said, I'll probably make it for myself, so I'd be happy to post it as an enhancement to the issues page in the next few days -- but I wanted to check first that there was no conensus that this was a bad idea.

This doesn't touch on the question of a ~/.pandoc path, which also seems like a good idea, but seems like a separate issue.

Thoughts?

Best,
Jesse

--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.
John MacFarlane | 3 Feb 01:50 2011
Picon

Re: paths to template files

+++ Jesse Rosenthal [Feb 02 11 15:37 ]:
>    Hello,
>    On Wednesday, January 27, 2010 4:53:59 AM UTC-5, Joost Kremers wrote:
> 
>      A slightly different approach, but with more flexibility, might be
>      to use profiles. These would be files somewhere under ~/.pandoc
>      containing pandoc settings. Instead of specifying all settings on
>      the command line each time you run pandoc, you'd then just say
>      `pandoc --profile=<my_profile> <input_file>'.
> 
>    Sorry to dig up an old thread, but I was wondering if this was
>    officially decided against. I'd be happy to put something together to
>    allow it -- I, at least, would find it *extremely* useful (I have a few
>    very different LaTeX templates I use often) so I'd probably make the
>    patches for myself anyway. I was thinking of just using the same format
>    as in the configuration files for the Joost Kremer's pandoc emacs mode,
>    unless there's any objection. And any options passed together with the
>    profile would take precedence. (I imagine the opt would just be
>    `--profile='.)
>    Anyway, as I said, I'll probably make it for myself, so I'd be happy to
>    post it as an enhancement to the issues page in the next few days --
>    but I wanted to check first that there was no conensus that this was a
>    bad idea.
>    This doesn't touch on the question of a ~/.pandoc path, which also
>    seems like a good idea, but seems like a separate issue.
>    Thoughts?

No, it's not officially decided against, but I'm conservative in
making changes.  If you're going to write a patch anyway, I'd take
a look, but I'm not yet sold on the idea.

In this case, my thought is that there's little need to add this
functionality to pandoc, when you can easily define a shell alias or write a
small shell wrapper to do the same thing. For example, in zsh,

alias 'pandoc-lecture'='pandoc -s -S -t latex --template=~/.pandoc/lecture.tex'

Or with a POSIX shell script:

#!/bin/sh
pandoc -s -S -t latex --template=~/.pandoc/lecture.tex "$ <at> "

What would profiles do that this couldn't?

John

Jesse Rosenthal | 3 Feb 02:22 2011

Re: paths to template files

On Wed, 02 Feb 2011 16:50:11 -0800, John MacFarlane
<fiddlosopher@...> wrote:
> No, it's not officially decided against, but I'm conservative in
> making changes.  

Fair enough -- it's a philosophy that has served the project well.

> In this case, my thought is that there's little need to add this
> functionality to pandoc, when you can easily define a shell alias or write a
> small shell wrapper to do the same thing.
> ...
> What would profiles do that this couldn't?

In technical terms, nothing -- but perhaps they might offer a slight
bump in user ease/comfort. For example, I find git more pleasant to use
now that there aren't 50 git-* commands, even if the funcionality is the
same. And since I try to keep the same setup on different computers, my
various scripts (or my one wrapper that reads the opt and acts
accordingly) would be one less thing to keep in sync. All with no change
to the underlying markup languages, and invisible to anyone who doesn't
care to use it.

Of course, I'm not sure whether this is a feature that others would even
care to use. If not, it's a moot point. And even if so, it's a
relatively small point. In any case, I'll post something on the tracker
when I'm happy with it.

Thanks,
Jesse

Joost Kremers | 3 Feb 09:25 2011

Re: paths to template files

On Wed, Feb 02, 2011 at 08:22:40PM -0500, Jesse Rosenthal wrote:
> Of course, I'm not sure whether this is a feature that others would even
> care to use.

if i may offer my two cents on the point: i certainly believe it's a feature
that could be of use to others. one of the reasons i wrote pandoc-mode for emacs
is that i found it cumbersome to have to remember to type all options everytime
i invoke pandoc. it's not much of a problem in a single session, because you can
simply use the up key in the shell to recall the previous command, but it's more
cumbersome if you work on a text over a longer period of time and on different
computers.

however, the only argument i have for building it into pandoc rather than using
a shell alias or wrapper is that that's about the last thing i'd think of... in
fact, it never occurred to me that that is a possibility at all.

--

-- 
Joost Kremers
Life has its moments

John MacFarlane | 3 Feb 16:55 2011
Picon

Re: paths to template files

+++ Jesse Rosenthal [Feb 02 11 20:22 ]:
> On Wed, 02 Feb 2011 16:50:11 -0800, John MacFarlane
<fiddlosopher@...> wrote:
> > No, it's not officially decided against, but I'm conservative in
> > making changes.  
> 
> Fair enough -- it's a philosophy that has served the project well.
> 
> > In this case, my thought is that there's little need to add this
> > functionality to pandoc, when you can easily define a shell alias or write a
> > small shell wrapper to do the same thing.
> > ...
> > What would profiles do that this couldn't?
> 
> In technical terms, nothing -- but perhaps they might offer a slight
> bump in user ease/comfort. For example, I find git more pleasant to use
> now that there aren't 50 git-* commands, even if the funcionality is the
> same. And since I try to keep the same setup on different computers, my
> various scripts (or my one wrapper that reads the opt and acts
> accordingly) would be one less thing to keep in sync. All with no change
> to the underlying markup languages, and invisible to anyone who doesn't
> care to use it.

With profiles, you'd have to keep the profiles in your ~/.pandoc
directory in sync.

With shell scripts, you'd have to keep the scripts in sync.

With shell aliases, you'd have to keep your .zshrc in sync.

I don't see a big difference here!

I also don't see a big "memory" difference. With profiles, you've got to
remember the name of the profile; with shell scripts/aliases, you've got to
remember the specialized command name. Either way, you can easily look it up.

John

Kenneth Reitz | 3 Feb 22:59 2011
Picon

Python Pandoc Wrapper

Hi there,

I released a fairly simple, but quite useful Pandoc wrapper for
Python:

    Pyandoc; https://github.com/kennethreitz/pyandoc

I'd love to get it added to the Pandoc Extras page.

John MacFarlane | 4 Feb 01:50 2011
Picon

Re: Python Pandoc Wrapper

Sure - added!

+++ Kenneth Reitz [Feb 03 11 13:59 ]:
> Hi there,
> 
> I released a fairly simple, but quite useful Pandoc wrapper for
> Python:
> 
>     Pyandoc; https://github.com/kennethreitz/pyandoc
> 
> I'd love to get it added to the Pandoc Extras page.
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss@...
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe@...
> For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.
> 


Gmane