> * List all files in dir (version of Seb)
>
> Just to show, this code prints a semi-colon after every filename.
>
> #+srcname: graph-files-seb2
> #+begin_src sh :results vector :var dir=graph-dir
> find $dir -type f -print |\
> while read -r name
> do
> echo "\"${name##*/}\";"
> done
Nick Dokos wrote:
> ...
> It is called with a nil separator so it uses its "smart" mode and counts
> one or more whitespace characters as the separator (I wonder
> what would happen with a filename that contains a comma :-)
>
Answer: nothing much.
Please disregard the comma comment: flippant st
Sébastien Vauban wrote:
> ...
> * List all files in dir (version of Seb)
>
> My code was a bit more complex... because I need to be able to correctly take
> care of filenames containing spaces inside them (I'm on Windows, I never do
> such a thing, but there are well spaces on the files I wanna
Hi Eric,
First, thanks for answering this open thread!
"Eric Schulte" wrote:
> I haven't followed this discussion very closely, but I'm not sure why it
> would be necessary to pass data through STDIN rather than through a variable
> or an external file.
I'll comment on the full problem (or solut
Hi,
I haven't followed this discussion very closely, but I'm not sure why it
would be necessary to pass data through STDIN rather than through a
variable or an external file.
I took a shot at the dot graph example you proposed, the following works
for me over a simple example directory.
Best --
Hi Dan,
Dan Davison wrote:
> Cool post. I hope someone has some good ideas in this thread. Some quick
> responses / questions below.
>
>> Note, in the latter code block, that I did not even tried to really chain
>> steps 2 and 3: I'm rewriting step 3, including step 2 inside it.
>>
>> *I certainly
Hi Dan,
Myself quickly reacting on this...
Dan Davison wrote:
> Cool post. I hope someone has some good ideas in this thread.
Thanks. Once solved, this one (and many more experiments I'm jotting down)
could become "case studies" on Worg, or so.
> Some quick responses / questions below.
>
>> #+T
Hi Seb,
Cool post. I hope someone has some good ideas in this thread. Some quick
responses / questions below.
> #+TITLE: Document a shell script as separate blocks
> #+DATE: 2011-02-04
> #+LANGUAGE: en_US
>
> * Abstract
>
> When writing shell scripts, I'd like to kill *two* birds with o
