From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarmo Hurri Subject: Re: New Beamer environment selection problem Date: Mon, 02 May 2016 11:37:45 +0300 Message-ID: <87twigdfdy.fsf@iki.fi> References: <878tzzv26g.fsf@iki.fi> <87k2jjl64z.fsf@saiph.selenimh> <87bn4v1887.fsf@iki.fi> <87k2jhieql.fsf@saiph.selenimh> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46352) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ax9Ms-0004jY-Oi for emacs-orgmode@gnu.org; Mon, 02 May 2016 04:38:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ax9Mh-0000Cs-5H for emacs-orgmode@gnu.org; Mon, 02 May 2016 04:38:09 -0400 Received: from plane.gmane.org ([80.91.229.3]:59337) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ax9Mg-0000BT-VC for emacs-orgmode@gnu.org; Mon, 02 May 2016 04:38:03 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ax9MV-0001Jf-62 for emacs-orgmode@gnu.org; Mon, 02 May 2016 10:37:51 +0200 Received: from host-137-163-18-130.edu.hel.fi ([137.163.18.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 May 2016 10:37:51 +0200 Received: from jarmo.hurri by host-137-163-18-130.edu.hel.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 May 2016 10:37:51 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Nicolas Goaziou writes: Greetings. >> Debugger entered--Lisp error: (wrong-number-of-arguments max 0) >> max() >> apply(max nil) >> org-fast-tag-selection(nil nil nil nil) >> org-set-tags() >> org-beamer-select-environment() >> call-interactively(org-beamer-select-environment nil nil) >> command-execute(org-beamer-select-environment) > > Would the following patch solve the issue? Instead of applying the patch to my current org source, I just pulled the latest git version and the problem seems to have dissappeared. So assuming that you already applied the patch to the latest git version, yes this patch solved the issue. Thanks a lot, once again! Jarmo