emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: What does the _ in `(defun org-element-section-parser (_) ...)' stands for?
Date: Thu, 11 Feb 2016 12:33:34 -0500	[thread overview]
Message-ID: <8760xvrw29.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87h9hfgoki.fsf@gmail.com

Thorsten Jolitz <tjolitz@gmail.com> writes:

> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> On Wed, Feb 10, 2016 at 3:13 PM, Thorsten Jolitz <tjolitz@gmail.com>
>> wrote:
>>
>>     #+BEGIN_SRC emacs-lisp
>>     (defun my-foo (_)
>>     "Hello World.
>>     Argument _ unknown argument."
>>     (+ 1 1))
>>     #+END_SRC
>>
>> strange. in Emacs 25.1, I am pretty sure I get no errors from
>> checkdoc.
>
> Maybe not so strange, since I'm on:
>
> ,----
> | GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.6)
> |  of 2015-09-10 on foutrelis
> `----
>
> And I thought with Archlinux I'm always up-to-date ...

Unless you build your own from the upstream git repo, you can never be
up to date; even so, it depends on how often you build - I build from
upstream every six months or so and my current version is

GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.15) of
2015-08-16

It's probably time to rebuild...

--
Nick

  parent reply	other threads:[~2016-02-11 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 17:45 What does the _ in `(defun org-element-section-parser (_) ...)' stands for? Thorsten Jolitz
2016-02-09 18:59 ` John Kitchin
2016-02-10 20:13   ` Thorsten Jolitz
2016-02-10 20:47     ` John Kitchin
2016-02-11 17:10       ` Thorsten Jolitz
2016-02-11 17:20         ` John Kitchin
2016-02-11 17:33         ` Nick Dokos [this message]
2016-02-14 16:45           ` John Kitchin

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=8760xvrw29.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@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).