[O] ob-haskell evaluation needs inf-haskell but it does not exist

2017-11-11 Thread stardiviner
When I execute the following Haskell src block:

```

#+BEGIN_SRC haskell :session :tangle "Data/Code/hello_world.hs"
main :: IO ()
main = do
  putStrLn "Hello, World!"
#+END_SRC
```

It reports error:

```

Debugger entered--Lisp error: (file-missing "Cannot open load file" "No
such file or directory" "inf-haskell")
  require(inf-haskell)
  org-babel-haskell-initiate-session(nil ((:colname-names)
(:rowname-names) (:result-params "replace") (:result-type . value)
(:results . "replace") (:exports . "code") (:cache . "no") (:noweb .
"no") (:hlines . "no") (:padlines . "no") (:session) (:tangle .
"Data/Code/hello_world.hs")))
  org-babel-execute:haskell("main :: IO ()\nmain = do\n  putStrLn
\"Hello, World!\"" ((:colname-names) (:rowname-names) (:result-params
"replace") (:result-type . value) (:results . "replace") (:exports .
"code") (:cache . "no") (:noweb . "no") (:hlines . "no") (:padlines .
"no") (:session) (:tangle . "Data/Code/hello_world.hs")))
  org-babel-execute-src-block(nil ("haskell" "main :: IO ()\nmain =
do\n  putStrLn \"Hello, World!\"" ((:colname-names) (:rowname-names)
(:result-params "replace") (:result-type . value) (:results . "replace")
(:exports . "code") (:tangle . "Data/Code/hello_world.hs") (:session)
(:padlines . "no") (:hlines . "no") (:noweb . "no") (:cache . "no")) ""
nil 1127 "(ref:%s)"))
  org-ctrl-c-ctrl-c(nil)
  funcall-interactively(org-ctrl-c-ctrl-c nil)
  call-interactively(org-ctrl-c-ctrl-c nil nil)
  command-execute(org-ctrl-c-ctrl-c)
```   




Re: [O] Org-mode link returned path is truncated when contains space

2017-11-11 Thread numbch...@gmail.com
sorry for delay reply. I'm cleaning up my Org tasks, found this task. this
issue seems fixed.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

On Tue, Jun 6, 2017 at 6:49 PM, Nicolas Goaziou 
wrote:

> Hello,
>
> "numbch...@gmail.com"  writes:
>
> > I checked Org-mode package version with `org-version`, get `9.0.7`, still
> > have this issue. I updated to latest org-mode ELPA version.
>
> Odd. You may have better luck with Org 9.0.8 then. In particular, commit
> 2d29269bb1b9af08011e091913798b6598e4b156 should prevent path from being
> truncated.
>
> Please report back if it works better (or not).
>
> Regards,
>
> --
> Nicolas Goaziou
>


Re: [O] function for inserting a block

2017-11-11 Thread numbch...@gmail.com
+1 I added a snippet for ` wrote:

> Carsten Dominik  writes:
>
> > I have always come down on the side of NOT breaking backward
> > compatibility unless we really HAVE TO in order to make progress. The
> > reason for this bias is because most Org users are not reading this
> > maling list and just want the system to function and to continue to
> > function the way they are used to, while it is hopefully improving. It
> > will stop them from upgrading if such breakage happens too often.
> >
> > So I would support reimplement the expansion (including
> > org-try-structure-completion for people who use that in custom code),
> > if possible of course on the back of one of the built-in expansion
> > systems in Emacs, before pushing this change out in a release. I would
> > certainly reimplement this in some way for myself, because using these
> > abbreviations is already hardcoded in my spine, I think.
>
> I agree. I support removing redundant code behind the scenes, but I also
> think we should preserve backwards compatibility in the user interface.
> A fair number of people around here have been using Org Mode for more
> than a decade, and, for better or for worse, everything about the user
> interface is now hardwired in their brains.
>
> In short, we have a time-saving expansion system that works well for
> lots of people. I support re-implementing it on top of another snippet
> engine but also leaving it in place until a suitable replacement is
> ready.
>
> Matt
>
>
>


Re: [O] function for inserting a block

2017-11-11 Thread Matt Lundin
Carsten Dominik  writes:

> I have always come down on the side of NOT breaking backward
> compatibility unless we really HAVE TO in order to make progress. The
> reason for this bias is because most Org users are not reading this
> maling list and just want the system to function and to continue to
> function the way they are used to, while it is hopefully improving. It
> will stop them from upgrading if such breakage happens too often.
>
> So I would support reimplement the expansion (including
> org-try-structure-completion for people who use that in custom code),
> if possible of course on the back of one of the built-in expansion
> systems in Emacs, before pushing this change out in a release. I would
> certainly reimplement this in some way for myself, because using these
> abbreviations is already hardcoded in my spine, I think.

I agree. I support removing redundant code behind the scenes, but I also
think we should preserve backwards compatibility in the user interface.
A fair number of people around here have been using Org Mode for more
than a decade, and, for better or for worse, everything about the user
interface is now hardwired in their brains. 

In short, we have a time-saving expansion system that works well for
lots of people. I support re-implementing it on top of another snippet
engine but also leaving it in place until a suitable replacement is
ready.

Matt




[O] Applescript help

2017-11-11 Thread Jay Iyer
Hi, in my Org workflow, I am trying to use the do-applescript function to
hide an active Emacs session.  Can you tell me what I am doing wrong with
the following that I think should work but is not?  Thanks. -jay

(do-applescript "tell application \"Finder\" set visible of application
process \"Emacs\" to false")


Re: [O] Leslie Lamport has a foot in the 21st century

2017-11-11 Thread Adonay Felipe Nogueira
An interesting subject.

On sidenote, I'm writing an introduction guide to writting documents in
either Org mode or LaTeX, for writers, scientists and students
([1]). It's currently in Brazilian Portuguese, but of course I might
translate it to English and also accept contributions.

[1] .

Marcin Borkowski  writes:

> Well, one might think that after about 20 years, LaTeX 2.09 should be
> already dead.  It's not.  Academia has a lot of inertia.  So we're
> probably stuck with LaTeX2e (for better or for worse) for at least
> several decades.
>
> Best,

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.



Re: [O] function for inserting a block

2017-11-11 Thread Thomas S. Dye

Eric Abrahamsen writes:

> Rasmus  writes:
>
>> Hi Eric,
>>
>> Eric Abrahamsen  writes:
>>
 Also, Eric, it seems that org-structure-template-alist only supports a
 single letter for short-hands (the car of an entry in
 org-structure-template-alist is a char).  I used to have blocks like ">>
>>> I hadn't thought of that. Really, all I ever wanted was to wrap things
>>> in blocks...
>>>
>>> I don't see any reason why org-structure-template-alist couldn't go back
>>> to using string keys. Then we could use read-string, and wouldn't have
>>> to have special  behavior -- a string that didn't exist in the
>>> alist could just be used literally to make a block.
>>
>> I’d prefer that.  For some special blocks, a few characters might makes it
>> more intuitive, e.g. "def" → "definition", "hyp" → "hypothesis" etc.
>
> Here's the simplest solution.
>
> There still remains the fact that `org-structure-template-alist' has
> changed format, and `org-try-structure-completion' no longer exists.
> That may still annoy some people who were using the internals of the
> process, but...

Would something like this work?

(defun org-try-structure-completion ()
  (tempo-complete-tag))

All the best,
Tom

--
Thomas S. Dye
http://www.tsdye.com