Re: [O] table export to same buffer

2013-08-03 Thread Nicolas Goaziou
Hello,

Rustom Mody rustompm...@gmail.com writes:

 The context is writing C with C mode (or haskell with haskell-mode python
 with python-mode etc) ie the user is not using orgmode.  That is why I
 mentioned orgtbl, ie org table editing facilities are needed but the major
 mode is something else.

 However here some pre and postprocessing is also probably required.
 Something like an automation of the following:

 1. Editing a large struct spec in C -- major mode is C-mode
 2. Select the region (may even be a rectangle)
 3. Paste into an org-mode buffer
 4. Run C-c | on region
 5. Edit table as required
 6. org-table-export in desired format to a file F
 7. Visit F
 8. Copy/Cut F (if necessary as rectangle)
 9. Go back to original C-mode buffer and paste

There's also `org-export-replace-region-by'.


Regards,

-- 
Nicolas Goaziou



Re: [O] org-export-current-backend variable and org-mode 8

2013-08-03 Thread Nicolas Goaziou
Hello,

Christophe Rhodes cs...@cantab.net writes:

 The `by-backend' macro in Brett Viren's message upthread?  Personally I
 don't consider that sufficient, because it feels very fragile: a simple
 renaming of org-mode internal variables, or turning on lexical binding,
 and the macro will no longer work.  (If you mean some other
 `by-backend', I haven't seen it).

I thought `by-backend' was in core already. Anyway, if it is, we'll make
sure it will not be fragile anymore.

 Subject: [PATCH] ox: restore org-export-current-backend variable

 * lisp/ox.el (org-export-current-backend): new variable.
 (org-export-as): bind it.

Applied a slightly different version. Thank you.


Regards,

-- 
Nicolas Goaziou



Re: [O] table export to same buffer

2013-08-03 Thread Thorsten Jolitz
Rustom Mody rustompm...@gmail.com writes:

 Sebastien Vauban wrote

 On Fri, Aug 2, 2013 at 10:53 PM, Rustom Mody rustompm...@gmail.com
 wrote:

 Is it possible to export an orgmode table not to a new file but
 overwriting the org table in the same buffer?

 Context is editing source code which contains a largeish table
 of (say) constants. Editing is done with orgtbl minor mode.

 When done it should become back the table in the natural
 format of the programming language

 [For simplicity lets just say csv will do]

 Using an Org Babel code block (which you have to write, of course)
 taking as input your table, and outputting your constants in the
 wished format should do what you're looking for, right?

 I dont think so. The context is writing C with C mode (or haskell with
 haskell-mode python with python-mode etc) ie the user is not using
 orgmode.  That is why I mentioned orgtbl, ie org table editing
 facilities are needed but the major mode is something else.

 However here some pre and postprocessing is also probably required.
 Something like an automation of the following:

 1. Editing a large struct spec in C -- major mode is C-mode
 2. Select the region (may even be a rectangle)
 3. Paste into an org-mode buffer
 4. Run C-c | on region
 5. Edit table as required
 6. org-table-export in desired format to a file F
 7. Visit F
 8. Copy/Cut F (if necessary as rectangle)
 9. Go back to original C-mode buffer and paste

Another possibility is to make your source code file an 'outshine' file
(activate outline-minor-mode with outshine.el extensions and structure
it with outcommented Org-mode headlines), because then you get many of
these steps for free (see
[[http://orgmode.org/worg/org-tutorials/org-outside-org.html][Org-mode
outside Org-mode]] on Worg for more info about outshine.el and
outorg.el).

This way, your source code file really _is_ an Org-mode file too, you
switch between the two views on the same file with 'M-# M-#' and 'M-#'.

I can give you an example without changing buffer while writing this
email, since 'outorg' works with message-mode too, i.e. doing 'M-# M-#'
in a message-mode buffer lets me write my email in full Org-mode.

Lets insert a table with constants:

#+tblname: consts
| constant |   value |
|--+-|
| conway   | 1.30357 |
| pi   | 3.14159 |
| e| 2.71828 |

#+name: tbl2lst
#+header: :var table=consts
#+header: :results value list verbatim :wrap SRC picolisp
#+begin_src emacs-lisp
 `(prog (scl 5) (setq lst (car ',table)))
#+end_src

#+results: tbl2lst
#+BEGIN_SRC picolisp
  (prog (scl 5) (setq lst (car (quote ((constant value) hline (conway
  1.30357) (pi 3.14159) (e 2.71828))
#+END_SRC

So the steps are:

 1. Make your source file an outshine file
 2. Edit it as Org-file (with 'M-# M-#' outorg-edit-as-org)
 3. Go back to the source view  (with 'M-#' outorg-copy-edits-and-exit)

Assume I'm editing a PicoLisp source file and want to introduce
constants the easy way (in an Org-mode table). Then in step (2) I would
add the table 'consts' and the Emacs Lisp source-block 'tbl2lst'. When
going back to the source view, the table and the source block will be
converted to PicoLisp comments.

No so the results block, because outorg recognizes its a PicoLisp block
and will convert it back to source code. Thus in the Emacs Lisp block I
use the table as variable that holds a nested list structure and
transform this nested list into a structure of my target programming
language, let it be PicoLisp or C or whatever. This should be much
easier than parsing the table itself.

Then everytime you want to edit the constants, you simply switch to
Org-mode view, edit the Org table, eval the Emacs Lisp source-block, and
switch back to PicoLisp source view.

--
cheers,
Thorsten




[O] org-open-link-from-string in a program

2013-08-03 Thread Eric Abrahamsen
I'm trying to write a small function that programmatically follows a
link to a gnus message, then calls
`gnus-summary-wide-reply-with-original' to start a reply to that
message. It seemed like `org-open-link-from-string' (after extracting
the address part from the link) would be the right choice, but I'm
seeing odd behavior.

When gnus sets up the reply buffer it also adds several hooks and
actions for restoring windows and marking messages as responded-to, etc,
and these hooks and actions depend on the value of (current-buffer) when
the reply was initiated. That's supposed to be the gnus summary buffer.

When I call all this from a function, however, (current-buffer)
continues to return the org buffer I started in, even after the link was
opened, which confuses gnus, and me. What I mean is this:

(let ((addr the-address-part-of-the-link))
   (org-open-link-from-string addr)
   (message %s (current-buffer)) ; returns the org buffer I started in
   (call-interactively
 'gnus-summary-wide-reply-with-original))

There must be something I'm misunderstanding about how buffers work when
you're doing something non-interactive. If I manually eval the
org-open-link-from-string statement, I end up in the summary buffer,
obviously, and all works fine.

What am I not getting?

Thanks!
Eric
  




Re: [O] org-open-link-from-string in a program

2013-08-03 Thread Thorsten Jolitz
Eric Abrahamsen e...@ericabrahamsen.net writes:

 I'm trying to write a small function that programmatically follows a
 link to a gnus message, then calls
 `gnus-summary-wide-reply-with-original' to start a reply to that
 message. It seemed like `org-open-link-from-string' (after extracting
 the address part from the link) would be the right choice, but I'm
 seeing odd behavior.

 When gnus sets up the reply buffer it also adds several hooks and
 actions for restoring windows and marking messages as responded-to, etc,
 and these hooks and actions depend on the value of (current-buffer) when
 the reply was initiated. That's supposed to be the gnus summary buffer.

 When I call all this from a function, however, (current-buffer)
 continues to return the org buffer I started in, even after the link was
 opened, which confuses gnus, and me. What I mean is this:

 (let ((addr the-address-part-of-the-link))
(org-open-link-from-string addr)
(message %s (current-buffer)) ; returns the org buffer I started in
(call-interactively
  'gnus-summary-wide-reply-with-original))

 There must be something I'm misunderstanding about how buffers work when
 you're doing something non-interactive. If I manually eval the
 org-open-link-from-string statement, I end up in the summary buffer,
 obviously, and all works fine.

#+begin_src emacs-lisp
(defun org-open-link-from-string (s optional arg reference-buffer)
  Open a link in the string S, as if it was in Org-mode.
  [...snip...]
(org-open-at-point arg reference-buffer)
#+end_src

,--
| org-open-at-point is an interactive Lisp function in `org.el'.
|
| (org-open-at-point optional ARG REFERENCE-BUFFER)
|
| Open link at or after point.
| If there is no link at point, this function will search forward up to
| the end of the current line.
| Normally, files will be opened by an appropriate application.  If the
| optional prefix argument ARG is non-nil, Emacs will visit the file.
| With a double prefix argument, try to open outside of Emacs, in the
| application the system uses for this file type.
`--

Maybe because you call

,-
| (org-open-link-from-string addr)
`-

without ARG, Emacs is not visiting the file and thus its buffer does not
become current?

Anyway, when you're done - please share, this is quite interesting.

--
cheers,
Thorsten




Re: [O] org-open-link-from-string in a program

2013-08-03 Thread Eric Abrahamsen
Thorsten Jolitz tjol...@gmail.com writes:

 Eric Abrahamsen e...@ericabrahamsen.net writes:

 I'm trying to write a small function that programmatically follows a
 link to a gnus message, then calls
 `gnus-summary-wide-reply-with-original' to start a reply to that
 message. It seemed like `org-open-link-from-string' (after extracting
 the address part from the link) would be the right choice, but I'm
 seeing odd behavior.

 When gnus sets up the reply buffer it also adds several hooks and
 actions for restoring windows and marking messages as responded-to, etc,
 and these hooks and actions depend on the value of (current-buffer) when
 the reply was initiated. That's supposed to be the gnus summary buffer.

 When I call all this from a function, however, (current-buffer)
 continues to return the org buffer I started in, even after the link was
 opened, which confuses gnus, and me. What I mean is this:

 (let ((addr the-address-part-of-the-link))
(org-open-link-from-string addr)
(message %s (current-buffer)) ; returns the org buffer I started in
(call-interactively
  'gnus-summary-wide-reply-with-original))

 There must be something I'm misunderstanding about how buffers work when
 you're doing something non-interactive. If I manually eval the
 org-open-link-from-string statement, I end up in the summary buffer,
 obviously, and all works fine.

 #+begin_src emacs-lisp
 (defun org-open-link-from-string (s optional arg reference-buffer)
   Open a link in the string S, as if it was in Org-mode.
   [...snip...]
   (org-open-at-point arg reference-buffer)
 #+end_src

 ,--
 | org-open-at-point is an interactive Lisp function in `org.el'.
 |
 | (org-open-at-point optional ARG REFERENCE-BUFFER)
 |
 | Open link at or after point.
 | If there is no link at point, this function will search forward up to
 | the end of the current line.
 | Normally, files will be opened by an appropriate application.  If the
 | optional prefix argument ARG is non-nil, Emacs will visit the file.
 | With a double prefix argument, try to open outside of Emacs, in the
 | application the system uses for this file type.
 `--

 Maybe because you call

 ,-
 | (org-open-link-from-string addr)
 `-

 without ARG, Emacs is not visiting the file and thus its buffer does not
 become current?

Huh, interesting -- I had looked at that function, and assumed that the
what the arg did was to force a file that might otherwise be opened by
an external process to be opened in emacs. I still think that's what it
means (and adding a '(4) doesn't solve the problem), but there's other
stuff in there that might lead to a solution.

 Anyway, when you're done - please share, this is quite interesting.

I will! It's pretty much done, except for this one little bug.




Re: [O] org-open-link-from-string in a program

2013-08-03 Thread Thorsten Jolitz
Eric Abrahamsen e...@ericabrahamsen.net writes:

 Thorsten Jolitz tjol...@gmail.com writes:

 Eric Abrahamsen e...@ericabrahamsen.net writes:

 I'm trying to write a small function that programmatically follows a
 link to a gnus message, then calls
 `gnus-summary-wide-reply-with-original' to start a reply to that
 message. It seemed like `org-open-link-from-string' (after extracting
 the address part from the link) would be the right choice, but I'm
 seeing odd behavior.

[...]

 #+begin_src emacs-lisp
 (defun org-open-link-from-string (s optional arg reference-buffer)
   Open a link in the string S, as if it was in Org-mode.
   [...snip...]
  (org-open-at-point arg reference-buffer)
 #+end_src

 ,--
 | org-open-at-point is an interactive Lisp function in `org.el'.
 |
 | (org-open-at-point optional ARG REFERENCE-BUFFER)
 |
 | Open link at or after point.
 | If there is no link at point, this function will search forward up to
 | the end of the current line.
 | Normally, files will be opened by an appropriate application.  If the
 | optional prefix argument ARG is non-nil, Emacs will visit the file.
 | With a double prefix argument, try to open outside of Emacs, in the
 | application the system uses for this file type.
 `--

 Maybe because you call

 ,-
 | (org-open-link-from-string addr)
 `-

 without ARG, Emacs is not visiting the file and thus its buffer does not
 become current?

 Huh, interesting -- I had looked at that function, and assumed that the
 what the arg did was to force a file that might otherwise be opened by
 an external process to be opened in emacs. I still think that's what it
 means (and adding a '(4) doesn't solve the problem), but there's other
 stuff in there that might lead to a solution.

Yes, you are right about the meaning of ARG, I should have looked twice. 

 Anyway, when you're done - please share, this is quite interesting.

 I will! It's pretty much done, except for this one little bug.

I can imagine that this is very useful for managing phonecalls to be
made in the future...

-- 
cheers,
Thorsten




Re: [O] org-open-link-from-string in a program

2013-08-03 Thread Eric Abrahamsen
Thorsten Jolitz tjol...@gmail.com writes:

 Eric Abrahamsen e...@ericabrahamsen.net writes:

 Thorsten Jolitz tjol...@gmail.com writes:

 Eric Abrahamsen e...@ericabrahamsen.net writes:

 I'm trying to write a small function that programmatically follows a
 link to a gnus message, then calls
 `gnus-summary-wide-reply-with-original' to start a reply to that
 message. It seemed like `org-open-link-from-string' (after extracting
 the address part from the link) would be the right choice, but I'm
 seeing odd behavior.

 [...]

 #+begin_src emacs-lisp
 (defun org-open-link-from-string (s optional arg reference-buffer)
   Open a link in the string S, as if it was in Org-mode.
   [...snip...]
 (org-open-at-point arg reference-buffer)
 #+end_src

 ,--
 | org-open-at-point is an interactive Lisp function in `org.el'.
 |
 | (org-open-at-point optional ARG REFERENCE-BUFFER)
 |
 | Open link at or after point.
 | If there is no link at point, this function will search forward up to
 | the end of the current line.
 | Normally, files will be opened by an appropriate application.  If the
 | optional prefix argument ARG is non-nil, Emacs will visit the file.
 | With a double prefix argument, try to open outside of Emacs, in the
 | application the system uses for this file type.
 `--

 Maybe because you call

 ,-
 | (org-open-link-from-string addr)
 `-

 without ARG, Emacs is not visiting the file and thus its buffer does not
 become current?

 Huh, interesting -- I had looked at that function, and assumed that the
 what the arg did was to force a file that might otherwise be opened by
 an external process to be opened in emacs. I still think that's what it
 means (and adding a '(4) doesn't solve the problem), but there's other
 stuff in there that might lead to a solution.

 Yes, you are right about the meaning of ARG, I should have looked twice. 

 Anyway, when you're done - please share, this is quite interesting.

 I will! It's pretty much done, except for this one little bug.

 I can imagine that this is very useful for managing phonecalls to be
 made in the future...

Well this will only cover composing and replying to emails, but if you
have a function that automatically makes a phone call, I suppose it
would serve as a template...

Mostly I'm doing it because a full half of my work seems to be replying
to interminable emails, and I wanted something that would keep me in the
agenda as much as possible: hit a key on a TODO, type the email, send
it, and there you are back in the agenda again. It's turning out to be
a little more complicated than I thought!




Re: [O] org-open-link-from-string in a program

2013-08-03 Thread Thorsten Jolitz
Eric Abrahamsen e...@ericabrahamsen.net writes:

 Thorsten Jolitz tjol...@gmail.com writes:

 Eric Abrahamsen e...@ericabrahamsen.net writes:

 Thorsten Jolitz tjol...@gmail.com writes:

 Eric Abrahamsen e...@ericabrahamsen.net writes:
 I can imagine that this is very useful for managing phonecalls to be
 made in the future...

 Well this will only cover composing and replying to emails, but if you
 have a function that automatically makes a phone call, I suppose it
 would serve as a template...

did I write phonecalls? I meant emails, obviously, and I stop posting
for today and go out for walk ... ;)

 Mostly I'm doing it because a full half of my work seems to be replying
 to interminable emails, and I wanted something that would keep me in the
 agenda as much as possible: hit a key on a TODO, type the email, send
 it, and there you are back in the agenda again. It's turning out to be
 a little more complicated than I thought!

thats more of less what I imagined, and it definitely sounds useful.

-- 
cheers,
Thorsten




Re: [O] emphasis and monospace within one word

2013-08-03 Thread Nick Dokos
Rob Stewart robstewar...@gmail.com writes:

 The following:
 \texttt{PING}s ~PONG~s, \textbf{Foo}s *Foo*s, \emph{Bar}s /Bar/s.

 When exported to latex produces:
 \texttt{PING}s \textasciitilde{}PONG\textasciitilde{}s, \textbf{Foo}s
 *Foo*s, \emph{Bar}s /Bar/s.

 What I'd really like to be able to do in my org mode file is to have
 bold, verbatim, or italics substrings within one word. I.e. for the
 latex export to look like:

 \texttt{PING}s \texttt{PING}s, \textbf{Foo}s \textbf{Foo}s,
 \emph{Bar}s  \emph{Bar}s.

 Is there a way of coercing org-mode latex export in to playing nicely?


The following thread might help:

  http://thread.gmane.org/gmane.emacs.orgmode/72958/focus=73036

-- 
Nick




Re: [O] org-export-current-backend variable and org-mode 8

2013-08-03 Thread Achim Gratz
Nicolas Goaziou writes:
 Applied a slightly different version. Thank you.

Shouldn't d1d918100e be in maint?

Also, I don't think that nil should mean both export in progress with
an anonymous backend and no export in progress.  You've been
advertising the use of anonmous derived backends to customize exporting,
so to me it would make more sense if somehow there was a way to detect
that situation and then get the name of the parent backend instead.


Regards,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds




Re: [O] org-export-current-backend variable and org-mode 8

2013-08-03 Thread Nicolas Goaziou
Hello,

Achim Gratz strom...@nexgo.de writes:

 Nicolas Goaziou writes:
 Applied a slightly different version. Thank you.

 Shouldn't d1d918100e be in maint?

No. Back-end as defstructs is only in the master branch.

 Also, I don't think that nil should mean both export in progress with
 an anonymous backend and no export in progress.  You've been
 advertising the use of anonmous derived backends to customize exporting,
 so to me it would make more sense if somehow there was a way to detect
 that situation and then get the name of the parent backend instead.

A back-end, anonymous or not, may have no parent at all.

We can also store the full back-end object instead of its name. In this
case, an unnamed back-end is not the same as nil. Alas, this variable
was introduced for compatibility, which that solution kinda defeats.

Speaking about compatibility, previous export framework didn't have
anonymous back-ends. Handling the nil case would give us nothing more.


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTex Adjustments for Org-Export

2013-08-03 Thread Brian van den Broek
On Jul 31, 2013 8:28 AM, Jeff Rush jr...@taupro.com wrote:

 I'm trying to export a .org file to .pdf and although I've gotten past
 many formatting hurdles, I am stuck on two problems.


snip


 2) How can I change the basic formatting of paragraphs everywhere to

  a) omit the leading indent, and
  b) have a blank line between paragraphs

 Instead of this strange-looking style:

 This is a test paragraph
 of the following kind of thing.
 And so is this one.

 I want it to look like this:

 This is a test paragraph
 of the following kind of thing.
   And so is this one.

Hi all,

(Catching up on the traffic, so a bit late to the thread.)

I don't use org's export facilities, so I am not sure how and where to
object this into org's export process. But, the LaTeX way is to use the
parskip package.

Please do reconsider, though. Just about every book on my shelves follows
what you label a 'strange style,' for the good reason that the style you
favour can result in ambiguity. (A paragraph that ends a page, takes up the
entire last line and is followed by a new paragraph cannot be distinguished
from a paragraph that spans the page break.)

Best,

Brian vdB


Re: [O] table export to same buffer

2013-08-03 Thread William Henney
On Fri, Aug 2, 2013 at 11:52 PM, Rustom Mody rustompm...@gmail.com wrote:

 Sebastien Vauban wrote

 On Fri, Aug 2, 2013 at 10:53 PM, Rustom Mody rustompm...@gmail.comwrote:

 Is it possible to export an orgmode table not to a new file but
 overwriting the org table in the same buffer?

 Context is editing source code which contains a largeish table of (say)
 constants.
 Editing is done with orgtbl minor mode.
 When done it should become back the table in the natural format of the
 programming language
 [For simplicity lets just say csv will do]



 Using an Org Babel code block (which you have to write, of course) taking as
 input your table, and outputting your constants in the wished format should 
 do
 what you're looking for, right?


 I dont think so.
 The context is writing C with C mode (or haskell with haskell-mode python
 with python-mode etc) ie the user is not using orgmode.  That is why I
 mentioned orgtbl, ie org table editing facilities are needed but the major
 mode is something else.


What about a radio table using orgtbl-to-generic?

See Appendix 6 of the Org manual

Will


-- 

  Dr William Henney, Centro de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia


Re: [O] LaTex Adjustments for Org-Export

2013-08-03 Thread John Hendy
On Sat, Aug 3, 2013 at 3:49 PM, Brian van den Broek
brian.van.den.br...@gmail.com wrote:

 On Jul 31, 2013 8:28 AM, Jeff Rush jr...@taupro.com wrote:

 I'm trying to export a .org file to .pdf and although I've gotten past
 many formatting hurdles, I am stuck on two problems.


 snip


 2) How can I change the basic formatting of paragraphs everywhere to

  a) omit the leading indent, and
  b) have a blank line between paragraphs

 Instead of this strange-looking style:

 This is a test paragraph
 of the following kind of thing.
 And so is this one.

 I want it to look like this:

 This is a test paragraph
 of the following kind of thing.
   And so is this one.

 Hi all,

 (Catching up on the traffic, so a bit late to the thread.)

 I don't use org's export facilities, so I am not sure how and where to
 object this into org's export process. But, the LaTeX way is to use the
 parskip package.

 Please do reconsider, though. Just about every book on my shelves follows
 what you label a 'strange style,' for the good reason that the style you
 favour can result in ambiguity. (A paragraph that ends a page, takes up the
 entire last line and is followed by a new paragraph cannot be distinguished
 from a paragraph that spans the page break.)


True, though when it comes to that sort of thing I look at it from a
probability point of view:
- p(what you described happens): perhaps  1%, if even that high
- p(looking at default LaTeX format will make my eyes bleed): 100%

That was [mostly] a joke. I'm actually not clear from the text above
what is desired. The description says no leading indent and blank
line between, but the example text shows non-indent on first
paragraph, indent on second (which would void the page-span concern),
and no line break...

I take it you have literary experience, which I'm glad to have on the
list. Your comment made me consider that I often fiddle with what
seems to look nice, overlooking that some of these things have a very
specific purpose in terms of avoiding ambiguity or what you described
-- I'd never have thought of that!


John

 Best,

 Brian vdB



Re: [O] LaTex Adjustments for Org-Export

2013-08-03 Thread David Rogers
John Hendy jw.he...@gmail.com writes:

 That was [mostly] a joke. I'm actually not clear from the text above
 what is desired. The description says no leading indent and blank
 line between, but the example text shows non-indent on first
 paragraph, indent on second (which would void the page-span concern),
 and no line break...

At first, I didn't understand the original post, but when I took the
original request to mean no indent *on the first paragraph of the
chapter or section*, then the rest made more sense to me.

My take on the subject:

- indent is good if you want it;

- added blank line is good if you want it;

- both at once is never good; it's necessary to choose between extra
  blank OR indenting, and stick with your choice throughout a work;

- indenting the first paragraph of a chapter, or putting an extra blank
  line directly after the chapter heading, should both be
  eliminated. (Of course chapter headings should have suitable vertical
  space after them depending on the style - I'm talking about not also
  adding extra after that.)

- In either case, this means a special rule is needed: paragraphs should
  begin with indent, or with an added blank line - BUT not if this is
  the first paragraph.

-- 
David



Re: [O] LaTex Adjustments for Org-Export

2013-08-03 Thread Brian van den Broek
On Aug 3, 2013 9:26 PM, John Hendy jw.he...@gmail.com wrote:

 On Sat, Aug 3, 2013 at 3:49 PM, Brian van den Broek
 brian.van.den.br...@gmail.com wrote:
 
  On Jul 31, 2013 8:28 AM, Jeff Rush jr...@taupro.com wrote:
 
  I'm trying to export a .org file to .pdf and although I've gotten past
  many formatting hurdles, I am stuck on two problems.
 
 
  snip
 
 
  2) How can I change the basic formatting of paragraphs everywhere to
 
   a) omit the leading indent, and
   b) have a blank line between paragraphs
 
  Instead of this strange-looking style:
 
  This is a test paragraph
  of the following kind of thing.
  And so is this one.
 
  I want it to look like this:
 
  This is a test paragraph
  of the following kind of thing.
And so is this one.
 
  Hi all,
 
  (Catching up on the traffic, so a bit late to the thread.)
 
  I don't use org's export facilities, so I am not sure how and where to
  object this into org's export process. But, the LaTeX way is to use the
  parskip package.
 
  Please do reconsider, though. Just about every book on my shelves
follows
  what you label a 'strange style,' for the good reason that the style you
  favour can result in ambiguity. (A paragraph that ends a page, takes up
the
  entire last line and is followed by a new paragraph cannot be
distinguished
  from a paragraph that spans the page break.)
 


snip

 That was [mostly] a joke. I'm actually not clear from the text above
 what is desired. The description says no leading indent and blank
 line between, but the example text shows non-indent on first
 paragraph, indent on second (which would void the page-span concern),
 and no line break...

Indeed it does. I missed that reading on my phone. I don't see how I can
blame my strange typo on that though, so perhaps I ought just give up :-)

As I said, I don't export from org to latex, but I am puzzled. The style
you describe (and which the OP appears to display) is what LaTeX does for
me by default. I know that no leading indent and inter-paragraph separation
is a common desire, so I guess I let lazy thinking take over.

 I take it you have literary experience, which I'm glad to have on the
 list. Your comment made me consider that I often fiddle with what
 seems to look nice, overlooking that some of these things have a very
 specific purpose in terms of avoiding ambiguity or what you described
 -- I'd never have thought of that!

I care about typography and have come to embrace that Knuth, Lamport, and
that maintainers of all things TeXnical are rather better at it than am I.
It is hard to resist the urge to fiddle, but I try :-)

Best,

Brian vdB


Re: [O] org-open-link-from-string in a program

2013-08-03 Thread Eric Abrahamsen
Eric Abrahamsen e...@ericabrahamsen.net writes:

 I'm trying to write a small function that programmatically follows a
 link to a gnus message, then calls
 `gnus-summary-wide-reply-with-original' to start a reply to that
 message. It seemed like `org-open-link-from-string' (after extracting
 the address part from the link) would be the right choice, but I'm
 seeing odd behavior.

 When gnus sets up the reply buffer it also adds several hooks and
 actions for restoring windows and marking messages as responded-to, etc,
 and these hooks and actions depend on the value of (current-buffer) when
 the reply was initiated. That's supposed to be the gnus summary buffer.

 When I call all this from a function, however, (current-buffer)
 continues to return the org buffer I started in, even after the link was
 opened, which confuses gnus, and me. What I mean is this:

 (let ((addr the-address-part-of-the-link))
(org-open-link-from-string addr)
(message %s (current-buffer)) ; returns the org buffer I started in
(call-interactively
  'gnus-summary-wide-reply-with-original))

 There must be something I'm misunderstanding about how buffers work when
 you're doing something non-interactive. If I manually eval the
 org-open-link-from-string statement, I end up in the summary buffer,
 obviously, and all works fine.

Hmm, I tried sticking a (redisplay) after opening the link, thinking
that might reset what is considered the current buffer, and it still
doesn't do it!




Re: [O] Publishing long jpg urls fails with org-html-handle-links: Wrong type argument: stringp, nil

2013-08-03 Thread Vijayender

I'm on 7.9.3f. Let me wait up.

Thank you!

--
Regards
Vijayender


On 08/02/2013 03:04 PM, Noorul Islam K M wrote:

Vijayender kvijayen...@gmail.com writes:


Hi All

After the commit of
http://orgmode.org/w/?p=org-mode.git;a=commitdiff;h=55f4f921835bbf5d7b8e9dd82fe8dcfef2fac4e2
Looks like long urls for eg, the following doc are failing to html export. It
happens without any customization on emacs-24.3-3

* queue to stack
   - 
http://img22.fansshare.com/celebrity/photos/934_liv-tyler-arwen-lord-of-the-rings-2103158475.jpg


I am not getting this stack trace.

Org-mode version 8.0.6 (release_8.0.6-377-ga3375f @ 
/home/noorul/.emacs.d/site-lisp/org-mode/lisp/)
GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw scroll bars)
  of 2013-07-18 on noman

Thanks and Regards
Noorul


Are failing to export to html. The problem disappears on enclosing url with [[]]
or for a jpg url which is shorter for eg:
http://img22.fansshare.com/photos/livtyler/jtvr-armageddon-1577984889.jpg

The debug stack trace is:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
   string-match(width= nil)
   org-html-handle-links(#(  - [[http://img22.fansshare.com/celebrity/photos/934_liv-tyler-arwen-lord-of-the-rings-2103158475.jpg][http://img22.fansshare.com/celebrity/photos/934\\_liv-tyler-arwen-lord-of-the-rings-2103158475.jpg]]; 0 3 (list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 fontified t) 3 4 (face org-link fontified t list-item 18 list-struct ((18 2 -  nil nil nil 119)) 
list-prevs ((18)) list-context nil) 4 6 (face org-link) 6 10 (face org-link fontified t list-item 18 list-struct ((18 2 -  nil nil nil 119)) list-prevs ((18)) list-context nil org-protected t org-no-description nil) 10 11 (face org-link org-protected t org-no-description nil) 11 100 (face org-link fontified t list-item 18 list-struct ((18 2 -  nil nil nil 119)) list-prevs ((18)) list-context nil org-protected t org-no-description nil) 
100 101 (face org-link fontified t rear-nonsticky (mouse-face highlight keymap invisible intangible help-echo org-linked-text htmlize-link) list-item 18 list-struct ((18 2 -  nil nil nil 119)) list-prevs ((18)) list-context nil org-protected t org-no-description nil) 101 102 (face org-link fontified t rear-nonsticky (mouse-face highlight keymap invisible intangible help-echo org-linked-text htmlize-link) list-item 18 list-struct ((18 2 - 
 nil nil nil 119)) list-prevs ((18)) list-context nil org-protected t org-no-description nil) 102 103 (face org-link) 103 104 (face org-link) 104 107 (list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 fontified t face org-link) 107 108 (list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 fontified t face org-link) 108 109 (face org-link) 109 150 
(list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 fontified t face org-link) 150 151 (list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 fontified t face org-link) 151 152 (face org-link) 152 153 (list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 fontified t face org-link) 153 199 (list-context nil list-prevs 
((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 fontified t face org-link) 199 200 (list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 rear-nonsticky (mouse-face highlight keymap invisible intangible help-echo org-linked-text htmlize-link) fontified t face org-link) 200 201 (list-context nil list-prevs ((18)) list-struct ((18 2 -  nil nil nil 119)) list-item 18 rear-nonsticky 
(mouse-face highlight keymap invisible intangible help-echo org-linked-text htmlize-link) fontified t face org-link) 201 202 (face org-link) 202 203 (face org-link)) (:latex-image-options nil :exclude-tags (noexport) :select-tags (export) :publishing-directory nil :timestamp nil :expand-quoted-html t :html-table-tag table border=\2\ cellspacing=\0\ cellpadding=\6\ rules=\groups\ 
frame=\hsides\ :xml-declaration ((html . ?xml version=\1.0\ encoding=\%s\?) (php . ?php echo \?xml version=\\\1.0\\\ encoding=\\\%s\\\ ?\; ?)) :html-postamble auto :html-preamble t :html-extension html :inline-images maybe :convert-org-links t :agenda-style nil :style-extra  :style 
 :style-include-scripts t :style-include-default t :table-auto-headline t :tables t :time-stamp-file t :creator-info t :email-info nil :author-info t :email vkarnaty@localhost ...))
   byte-code(\203 .. )
   org-export-as-html(nil)
   call-interactively(org-export-as-html)
   org-export(nil)
   call-interactively(org-export nil nil)