emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] using #+call for inline results
Date: Wed, 29 Jun 2011 10:25:59 -0700	[thread overview]
Message-ID: <87sjqs5z2w.fsf@gmail.com> (raw)
In-Reply-To: <87wrg45zpg.fsf@gmail.com> (Eric Schulte's message of "Wed, 29 Jun 2011 10:12:27 -0700")

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

Hi Seb,

I have attempted to reproduce the two problems I've seen mentioned,
specifically

1. repeated prompts to evaluate code when `org-confirm-babel-evaluate'
   is set to nil

2. Org-mode files not being seen with Org set as the major mode

I've used the following minimal configuration

[-- Attachment #2: seb.el --]
[-- Type: application/emacs-lisp, Size: 239 bytes --]

[-- Attachment #3: Type: text/plain, Size: 118 bytes --]

which adds the problematic Org-mode file you included in a recent email
(attached) into the list of org-agenda-files.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #4: seb.org --]
[-- Type: text/x-org, Size: 854 bytes --]

#+TITLE:     Babel ECM
#+DATE:      2011-06-28
#+DESCRIPTION: 
#+KEYWORDS: 
#+LANGUAGE:  en_US
#+LaTeX_CLASS: mcreport
#+LaTeX_CLASS_OPTIONS: (final)
#+BABEL:     :eval never :engine msosql :cmdline -S cauchy -U sa -P LpmdlP -d pfi-paiestag -n -w 700 :results output :exports both :noweb yes

* Introduction

This library is an extensible *collection of* ready-made *code blocks*
for handling common tasks.

* "Generic" Transact-SQL

** Add a column into a table

#+srcname: add-column-in-table[table, column, type, nullability]
#+begin_src sql
  -- add column `$column' [if column does not exist yet]
  IF NOT EXISTS [SELECT *
                 FROM INFORMATION_SCHEMA.COLUMNS
                 WHERE TABLE_NAME = '$table'
                 AND COLUMN_NAME = '$column']
  BEGIN
      ALTER TABLE $table
      ADD $column $type $nullability
  END
#+end_src

[-- Attachment #5: Type: text/plain, Size: 3482 bytes --]


I have been unable to reproduce either of the problems you described.
Could you start with these two files and build a minimal example
demonstrating the bug which can be started with something along the
lines of
: emacs -Q -l seb.el

Once I can observer the behavior then I should have a chance to fix it.

Thanks -- Eric

Eric Schulte <schulte.eric@gmail.com> writes:

> "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
>
>> Hi Eric,
>>
>> Eric Schulte wrote:
>>>> Well, I have many other problems with this version (such as speed commands
>>>> not working anymore, yasnippet expansion not working anymore on TAB, some
>>>> files which say they're not in Org-agenda-files, etc.) but that's another
>>>> story.
>>>
>>> I don't understand, are you saying that all of the above problems are caused
>>> by the introduction of inline call lines? I have not experienced any of
>>> these problems.
>>
>> No, I just said I had many other little problems since the last git update.
>> Though, I did not know where they come from. Now, I am positive that it comes
>> from the LOB. See the ECM I sent yesterday, and the similar report done
>> yesterday by Darlan.
>>
>
> Hi Seb,
>
> I don't know what you are referencing above, but if the new LOB behavior
> is causing problems then I certainly want to help resolve them.  Can you
> link me to the "ECM" you mentioned, and to Darlan's report?
>
>>
>>>> About this, my only weirdness is that I had to confirm 12 times (yes, 12!)
>>>> that I wanted to execute the calls.
>>>>
>>>> I have this in my emacs config file for months
>>>>
>>>>         ;; don't be prompted on every code block evaluation
>>>>         (setq org-confirm-babel-evaluate nil)
>>>>
>>>> ... has this var become a local file variable?
>>>
>>> This has not become a buffer local variable and I can not reproduce your
>>> problem, could you please submit a minimal configuration with which I
>>> can reproduce this problem.
>>
>> When removing the Org file with the SQL code from my org-agenda-files, and
>> relaunching Emacs (on an updated git), I don't see that problem anymore...
>> Maybe related to the above problem, then.
>>
>
> Hmm, could you send me a copy (or minimal subset) of this offending
> Org-mode file that causes the multiple prompts?  Are you loading this
> file using `org-babel-lob-ingest'?
>
>>
>>>> Last thing: the questions in the echo area sometimes display the block name
>>>> in parentheses, sometimes not...
>>>>
>>>> - "Evaluate this emacs-lisp code block (square) on your system? (yes or no)"
>>>> - "Evaluate this emacs-lisp code block on your system? (yes or no)"
>>>
>>> When the code block has a name, the name is shown in parens, when the code
>>> block is not named no name is shown.
>>
>> What I did not understand, is that these messages appeared when running the
>> example file I took, where only one block is defined, and that block is named.
>> Hence, I'd expect to always see the same message, with the block name in
>> parentheses.
>>
>> Though, as I don't have to confirm anymore (the symptom disappeared), we can
>> put this in the fridge... but for the problem with the LOB file (see
>> thtp://www.mail-archive.com/emacs-orgmode@gnu.org/msg43083.html).
>>
>
> Oh, I see, the file in question is mentioned in this linked email.  I
> will take a look and see if I can reproduce locally.  Expect more from
> me on this today.
>
> Cheers -- Eric
>
>>
>> Best regards,
>>   Seb

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  reply	other threads:[~2011-06-29 17:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 11:07 [babel] using #+call for inline results Eric S Fraga
2011-06-22 16:23 ` Eric Schulte
2011-06-22 18:22   ` Eric S Fraga
2011-06-23  5:32     ` Eric Schulte
2011-06-23  8:10       ` Eric S Fraga
2011-06-23 13:49         ` Nicolas Goaziou
2011-06-23 15:39           ` chris.m.malone
2011-06-23 17:30           ` Eric S Fraga
2011-06-23 19:55             ` Nicolas Goaziou
2011-06-24  8:11               ` Eric S Fraga
2011-06-23  9:25       ` Christian Moe
2011-06-24 22:36         ` Eric Schulte
2011-06-25 19:33           ` Eric S Fraga
2011-06-26 11:56           ` Christian Moe
2011-06-27  0:14             ` Eric Schulte
2011-06-27  6:16               ` Christian Moe
2011-06-27 17:43                 ` Eric Schulte
2011-06-27 19:01                   ` Christian Moe
2011-06-28  8:04                   ` Sebastien Vauban
2011-06-28 20:31                     ` Eric Schulte
2011-06-29  7:40                       ` Sebastien Vauban
2011-06-29 17:12                         ` Eric Schulte
2011-06-29 17:25                           ` Eric Schulte [this message]
2011-06-27 17:09           ` Eric S Fraga
2011-06-27 18:45             ` Eric Schulte
2011-06-29 16:38               ` Eric S Fraga
2011-06-29 17:59                 ` Eric Schulte
2011-06-22 17:53 ` Juan Pechiar

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=87sjqs5z2w.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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).