From: Eric Schulte <schulte.eric@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: a minor patch to awk invocation
Date: Sat, 07 Jun 2014 11:17:45 -0400 [thread overview]
Message-ID: <87egz0d9dy.fsf@gmail.com> (raw)
In-Reply-To: 874mzxt3gl.fsf@Rainer.invalid
Achim Gratz <Stromeko@nexgo.de> writes:
> Eric Schulte writes:
>> Thanks for pointing out this shortcoming and for suggesting the
>> command-line variable assignment option. I've just pushed up a patch
>> which changes the behavior of awk code blocks to assign variables on the
>> command line, so the following now work.
>
> For whatever reason I now get errors from an awk invocation using
> standard input:
>
> --8<---------------cut here---------------start------------->8---
> tset: standard error: Inappropriate ioctl for device
>
> /bin/stty: standard input: Inappropriate ioctl for device
> /usr/bin/stty: standard input: Inappropriate ioctl for device
> --8<---------------cut here---------------end--------------->8---
>
> Additionally, C-c C-v C-v doesn't work correctly on many blocks and
> gives
>
> --8<---------------cut here---------------start------------->8---
> org-babel-expand-src-block: Wrong type argument: number-or-marker-p, nil
> --8<---------------cut here---------------end--------------->8---
>
I can't reproduce these problems. Could you provide examples, and maybe
a stack traces?
Thanks,
>
>
> Regards,
> Achim.
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)
next prev parent reply other threads:[~2014-06-07 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 18:12 a minor patch to awk invocation Greg Minshall
2014-06-06 16:52 ` Eric Schulte
2014-06-07 5:42 ` Greg Minshall
2014-06-07 5:46 ` Greg Minshall
2014-06-07 15:15 ` Eric Schulte
2014-06-07 19:05 ` Greg Minshall
2014-06-07 10:32 ` Achim Gratz
2014-06-07 15:17 ` Eric Schulte [this message]
2014-06-07 16:22 ` Achim Gratz
2014-06-07 17:00 ` Eric Schulte
2014-06-07 17:57 ` Achim Gratz
2014-06-13 6:37 ` Achim Gratz
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=87egz0d9dy.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=Stromeko@nexgo.de \
--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).