emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Torsten Wagner <torsten.wagner@gmail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: FengShu <tumashu@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: layout org-babel menu WAS: About org-babel menu
Date: Fri, 6 Apr 2012 10:51:56 +0900	[thread overview]
Message-ID: <CAPaq-gNVx1RNO=xOGKPQ5X-gL_OmG-Fv59OfC-CZSbpGwoeXwA@mail.gmail.com> (raw)
In-Reply-To: <87pqbm8i0t.fsf@gmx.com>

Hi,

for me the biggest "trouble" with babel is to remember the possible
keywords in the header for different languages.
There were a lot of ongoing syntax change which did not make it easier
for me to remember all this.
Thus a menu which is organised by languages offering all possible
settings for each language would be very helpful.
|
Python
|    |
|  export - code - result - both - none
|    |
|  tangle - no - yes- filename
|   |
|  result - value - output
|  |
| ...
|
...

Not sure how effectual this would be in a main menu. It would be
definitely awesome in a context menu

That would be (copied from worg) [*] indicates cursor position

#+NAME: factorial
#+BEGIN_SRC haskell [*] :results silent :exports code :var n=0

a context menu would appear presenting all possible header arguments for haskell

#+NAME: factorial
#+BEGIN_SRC haskell :results [*] :exports code :var n=0

a context menu presenting all possible values for the header argument
:results in haskell
I guess that together with the possibility to call this menu by
keyboard strokes or alternatively show the same infos in the
minibuffer would be a great win for babel and it would make many
questions here on the list unnecessary.
Furthermore, any change or extension in the syntax for a certain
language would be directly reflected to the end-user. E.g., If I
suddenly see the menu entry :exports 3dprint, I would be curious and
check it out on worg and the manual ;)

Totti



On 5 April 2012 21:44, Eric Schulte <eric.schulte@gmx.com> wrote:
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> On 28/03/12 01:07, Bastien wrote:
>>> Hi Rainer,
>>>
>>> Rainer M Krug <r.m.krug@gmail.com> writes:
>>>
>>>> So I would see it as a useful way of promoting babel (and therefore org-mode) and also as a
>>>> nice reminder of less frequently (but nevertheless usefull) functionality.
>>>
>>> Agreed.
>>>
>>> Is anyone volunteering for listing the items in such a menu for Babel?
>>>
>>> If so, I'm willing to implement this.
>> OK - let me start this.
>>
>> Org
>> |
>> + Babel
>>   |
>>   + edit
>>   |  |
>>   |  + open surce buffer (that C-c ')
>>   |  + insert source block skeleton
>>   |  + ...
>>   |  + ...
>>   |
>>   + tangle
>>   |  |
>>   |  + tangle buffer
>>   |  + inverse tangle
>>   |  + ...
>>   |  + ...
>>   |
>>   + evaluate
>>   |  |
>>   |  + evaluate code block
>>   |  + evaluate subtree
>>   |  + ...
>>   |  + ...
>>   |  + ...
>>   |  + ...
>>   |
>>   + help
>>   |  |
>>   |  + Link to info help on header arguments
>>   |  + Link to info help on how to enable languages
>>   |  + URL to language specific help on worg
>>   |  + ...
>>   |  + ...
>>
>>
>> So - At the moment this is a skeleton of the babel menu - Comments? forgotten commands (I assume
>> many?
>>
>
> Hi Rainer,
>
> Thanks for starting this.  It looks like a great skeleton.  Here are a
> couple of comments which I hope are helpful.
>
> To find more publicly available Babel function you can do C-c C-v h in
> an Org-mode buffer or run the org-babel-describe-bindings command
>
> There are two high level sub-menus which I may suggest be added to the
> above, namely "languages" and "library of babel", which could list
> information on available languages and list library of babel functions
> respectively.
>
> I'm not sure how menus are normally used, specifically how Emacs breaks
> functionality between the menu, configuration and help sub-systems.  It
> is possible that because of such boundaries both the "help" and
> "languages" submenus may not be appropriate.
>
> Two other pieces of menu content which occur to me are a list of the
> code blocks available in the current buffer including some information
> on each block (e.g., name, arguments,), and a way to show the user what
> the current file wide header arguments are -- note: there already exists
> a function for displaying this information on the code block level
> `org-babel-view-source-block-info' which may be sufficient.
>
> Cheers,
>
>>
>>>
>>> I'm not convince we should have a menu item to (de)activate each language though -- more a menu
>>> that exposes the basics.
>>
>> Agreed.
>>
>> Cheers,
>>
>> Rainer
>>
>>
>>
>>
>>>
>>> Thanks,
>>>
>
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte/
>

  reply	other threads:[~2012-04-06  1:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 13:22 About org-babel menu FengShu
2012-03-19 14:22 ` Eric Schulte
2012-03-19 14:41   ` Rainer M Krug
2012-03-19 14:52     ` Eric Schulte
2012-03-31  5:50       ` Torsten Wagner
2012-03-31  7:21         ` Nick Dokos
2012-04-01 16:34           ` Bernt Hansen
2012-04-01 20:26             ` Nick Dokos
2012-03-31  8:27         ` Bastien
2012-03-31 10:33           ` Yagnesh Raghava Yakkala
2012-03-19 15:03     ` Jonathan Leech-Pepin
2012-03-27 23:07     ` Bastien
2012-04-05  9:08       ` layout org-babel menu WAS: " Rainer M Krug
2012-04-05 12:44         ` Eric Schulte
2012-04-06  1:51           ` Torsten Wagner [this message]
2012-04-06  6:34             ` Rainer M Krug
2012-04-06  6:48               ` Thorsten
2012-04-06  6:58                 ` Rainer M Krug
2012-04-06  7:18                 ` Bastien
2012-04-06  9:29                   ` Thorsten
2012-04-06 15:40             ` Thomas S. Dye
2012-04-06 21:51             ` Eric Schulte
2012-04-08 21:19               ` Thomas S. Dye
2012-04-11  1:40                 ` Eric Schulte
2012-04-11  7:26                   ` Rainer M Krug
2012-04-11 13:59                     ` Eric Schulte
2012-04-11 20:12                       ` Thomas S. Dye
2012-04-13 12:45                         ` Eric Schulte
2012-04-13 19:37                           ` [bug?] Re: layout " Yagnesh Raghava Yakkala
2012-04-14 13:35                             ` Eric Schulte
2012-04-14 16:21                               ` Nick Dokos
2012-04-10  8:05               ` layout org-babel menu WAS: About " Rainer M Krug
2012-04-10 20:35                 ` Bastien
2012-04-11  7:10                   ` Rainer M Krug
2012-04-11  7:24                     ` Yagnesh Raghava Yakkala
2012-04-11  8:10                       ` Bastien
2012-04-11  8:11                     ` Bastien
2012-04-11  8:13                       ` Rainer M Krug
2012-04-11 13:51                         ` Eric Schulte
2012-04-11 13:43                       ` Eric Schulte

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to='CAPaq-gNVx1RNO=xOGKPQ5X-gL_OmG-Fv59OfC-CZSbpGwoeXwA@mail.gmail.com' \
    --to=torsten.wagner@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.schulte@gmx.com \
    --cc=tumashu@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).