From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: minor problem on major version number Date: Thu, 26 Jun 2014 12:14:42 -0400 Message-ID: <871tubsl59.fsf@alphaville.bos.redhat.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54177) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X0CKH-0000i1-7s for emacs-orgmode@gnu.org; Thu, 26 Jun 2014 12:15:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X0CK8-0007zy-Rr for emacs-orgmode@gnu.org; Thu, 26 Jun 2014 12:15:05 -0400 Received: from plane.gmane.org ([80.91.229.3]:48848) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X0CK8-0007zu-M2 for emacs-orgmode@gnu.org; Thu, 26 Jun 2014 12:14:56 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1X0CK7-0005my-CC for emacs-orgmode@gnu.org; Thu, 26 Jun 2014 18:14:55 +0200 Received: from nat-pool-bos-t.redhat.com ([66.187.233.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Jun 2014 18:14:55 +0200 Received: from ndokos by nat-pool-bos-t.redhat.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Jun 2014 18:14:55 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org I have some backward-compat code that does this: --8<---------------cut here---------------start------------->8--- ;;(setq major-version (string-to-number (nth 0 (split-string (org-version) "[.]")))) (setq major-version 8) (if (< major-version 8) (progn (require 'org-latex) ... (progn (require 'ox-latex) ... --8<---------------cut here---------------end--------------->8--- After last night's git pull, org-version returns "beta_8.3" which broke the major-version calculation above. I hardwired the org version major number above, but I was wondering if we could agree on some convention/method that will not break in the future - maybe an org-major-version function? Thanks, Nick