From: Rustom Mody <rustompmody@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Some orgtbl doc issues
Date: Sat, 31 Aug 2013 22:02:59 +0530 [thread overview]
Message-ID: <CAJ+TeoeV8QCD9P2HjpA1X+dduAR_CwyCAXRTbazjPTqGffjQwg@mail.gmail.com> (raw)
In-Reply-To: <1AA0B1B9-9A50-4289-84BD-F0F1E9E7FAFB@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4727 bytes --]
Well clearly the radio tables section reads better now. Further comments
inline.
Before that some general comments.
The Python list thread starting here
http://mail.python.org/pipermail/python-list/2013-July/653164.html
As you will see some python programmers (including emacsers!) seem to have
a need for something like this and dont seem to know about org. And by
extension one may assume other languages than python also. In short this
seems to be a general need.
So what is written below should be taken less from my own pov -- I am
hardly an org power-user but still a user -- than from the pov of a general
emacser -- a programmer who uses emacs and knows next to nothing about org
On Fri, Aug 30, 2013 at 10:16 PM, Carsten Dominik <carsten.dominik@gmail.com
> wrote:
> Hi Rustom,
>
> thanks for this.
>
> On 16.8.2013, at 16:30, Rustom Mody <rustompmody@gmail.com> wrote:
>
> > Ive recently been poking around in orgtbl mode and encountered some
> > issues. Not sure how much is my own lack of understanding and how
> > much there are some little doc issues.
> >
> > 1 Option names dont match
> > =========================
> >
> > - Its orgtbl-radio-table-templates in emacs
> > - Its orgtbl-radio-tables in doc Appendix A.6.2
>
> Fixed, thanks.
>
> >
> >
> > 2 Receiving string
> > ==================
> >
> > - Seems to be "RECEIVE ORGTBL"
>
> It is BEGIN RECEIVE ORGTBL followed by a table name. As the example in
> the manual shows. Does this have to be more explicit?
>
> > - String seems to be hardwired. Which may be ok if its by design.
>
> Yes, hardwired by design.
>
Not a problem in itself.
It becomes a problem in connection with the dfault value of
org-radio-table-templates which contains many instances of
BEGIN RECEIVE ORGTBL %n
and thereby suggests that that is changeable
> > - Not clear what is the relation of this string and
> > orgtbl-radio-templates
>
> The templates insert a BEGIN RECEIVE/END RECEIVE table template with
> *proper commenting* around it in different programming modes.
> I improved this in the docs.
>
> > - I find 1 space is fixed between RECEIVE and ORGTBL. Multiple
> > allowed between ORGTBL and table-name
>
> OK, I have removed this restriction.
>
> > - Its not clear from the doc whether its "RECEIVE ORGTBL" or
> > "/* RECEIVE ORGTBL"
>
> That depends on the programming mode. The documentation says that the
> lines must be comments in the current mode, I would think that this is
> clear enough.
>
Some languages (eg Python) have no multiline comment but have a multiline
string which is also ok to use
>
> > - Subtle interaction between # in org and host mode comment char -- #
> > in python, shell etc -- could do with some elaboration
>
> Can you propose something for the documentation?
>
> >
> >
> > 3 hook system
> > =============
> >
> > - What are the hooks for orgtbl?
> > - How do the org hooks relate to the orgtbl hooks?
> > - Note: orgtbl is for those who are not otherwise using orgmode
>
> What to you mean? Mode hooks, or hooks for specific functionality of the
> table? If table commands run hooks, the corresponding orgtbl commands will
> do so as well, because they simply call the table functions in an
> environment where the proper keys bindings are not accessible.
>
As I said at start of this mail, we are looking at orgtbl for otherwise
non-org users.
For that audience I was exploring whether vanilla org would work OTB
ie without any of my org-settings
also not the latest but one bundled with emacs
Since at that point I really could not understand
orgtbl-radio-table-templates and thought it had to be set I asked. As it
appears now, it works without any customization so the point is moot.
Nevertheless the general question is: If a non-org user of orgtbl needs to
set up minor-mode specific customization where is it to be done?
> orgtbl-mode is a standard minor mode and has `orgtbl-mode-hook', similar
> to all other minor modes. See the documentation of define-minor-mode. Do
> you feel the manual should say so? It does not document many other hooks
> in org either, because there are too many.
>
>
> >
> > 4 Long header line
> > ==================
> >
> > I could not figure out how to split a long
> > :#+ORGTBL: SEND... line
>
> It cannot be split.
>
There are programming related organizations for which something like
80-char lines is really not negotiable!
So I hope this can be considered as a feature request of course a very
minor one
Regards
>
> - Carsten
>
Speaking generally, maybe someone should respond to that python list thread.
It can be me however someone more org-knowledgeable may be more appropriate
:-)
Thanks and regards
Rusi
--
http://blog.languager.org
[-- Attachment #2: Type: text/html, Size: 6910 bytes --]
next prev parent reply other threads:[~2013-08-31 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 14:30 Some orgtbl doc issues Rustom Mody
2013-08-30 16:46 ` Carsten Dominik
2013-08-31 6:01 ` Rustom Mody
2013-08-31 16:32 ` Rustom Mody [this message]
[not found] ` <EC962964-FF55-49D0-820C-C5642649E89A@gmail.com>
[not found] ` <CAJ+TeoeCadjXQ-sKSDjXZ1WoQq_HSSDNCTTYTUFugYo3p1kzFg@mail.gmail.com>
[not found] ` <03A40E05-1CF6-4DE1-806C-58329BBBF6B0@gmail.com>
[not found] ` <CAJ+Teofg68pcujqwXgZyeZ5c9k7niqyj_vJgvu21XX_02zqCUQ@mail.gmail.com>
[not found] ` <83E12140-B647-4476-8BBB-706DDA1E8476@gmail.com>
[not found] ` <CAJ+Teocns0UDDfgyEDHvb_MHYBad+qsu0DwowyiEAdEOLZnm4A@mail.gmail.com>
[not found] ` <28171E40-3004-4C0C-B5E0-7E86822ECE46@gmail.com>
[not found] ` <CAJ+TeodniSbEv3HMA_Vs3byYBmC+fKoZvKJOrZYYJBpcOd1sHg@mail.gmail.com>
2013-09-03 17:02 ` Rustom Mody
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=CAJ+TeoeV8QCD9P2HjpA1X+dduAR_CwyCAXRTbazjPTqGffjQwg@mail.gmail.com \
--to=rustompmody@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).