Skip site navigation (1)Skip section navigation (2)
Date:      11 Sep 2005 23:42:20 -0000
From:      Mike Meyer <mwm@mired.org>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   ports/85995: New port: devel/pymacs, lets you write emacs extensions in python
Message-ID:  <20050911234220.4941.qmail@mired.org>
Resent-Message-ID: <200509112350.j8BNo7i2038889@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         85995
>Category:       ports
>Synopsis:       New port: devel/pymacs, lets you write emacs extensions in python
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 11 23:50:07 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Mike Meyer
>Release:        FreeBSD 5.4-STABLE i386
>Organization:
Meyer Consultign
>Environment:
System: FreeBSD bhuda.mired.org 5.4-STABLE FreeBSD 5.4-STABLE #9: Thu Aug 11 15:56:04 EDT 2005 mwm@bhuda.mired.org:/usr/src/sys/i386/compile/BHUDA i386

>Description:

You have to write emacs extensions in lisp. Unless you have pymacs
installed, anyway. Current versions of at least one other ports
software (devel/bicyclerepair) now depend on pymacs.

>How-To-Repeat:

Try writing them in something else! Or try installing the latest
version of the bicyclerepair software for use with emacs.

>Fix:

Commit the attached port.

# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#	pymacs
#	pymacs/pkg-plist
#	pymacs/pkg-message
#	pymacs/pkg-descr
#	pymacs/distinfo
#	pymacs/Makefile
#
echo c - pymacs
mkdir -p pymacs > /dev/null 2>&1
echo x - pymacs/pkg-plist
sed 's/^X//' >pymacs/pkg-plist << 'END-of-pymacs/pkg-plist'
X%%EMACS_SITE_LISPDIR%%/pymacs.el
X%%EMACS_SITE_LISPDIR%%/pymacs.elc
Xbin/pymacs-services
Xbin/rebox
X%%PYTHON_SITELIBDIR%%/Pymacs/pymacs.py
X%%PYTHON_SITELIBDIR%%/Pymacs/__init__.py
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/nncourriel.py
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/folder.py
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/__init__.py
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/nncourriel.pyc
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/folder.pyc
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/__init__.pyc
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/nncourriel.pyo
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/folder.pyo
X%%PYTHON_SITELIBDIR%%/Pymacs/Nn/__init__.pyo
X%%PYTHON_SITELIBDIR%%/Pymacs/Rebox/__init__.py
X%%PYTHON_SITELIBDIR%%/Pymacs/Rebox/rebox.py
X%%PYTHON_SITELIBDIR%%/Pymacs/Rebox/__init__.pyc
X%%PYTHON_SITELIBDIR%%/Pymacs/Rebox/rebox.pyc
X%%PYTHON_SITELIBDIR%%/Pymacs/Rebox/__init__.pyo
X%%PYTHON_SITELIBDIR%%/Pymacs/Rebox/rebox.pyo
X%%PYTHON_SITELIBDIR%%/Pymacs/pymacs.pyc
X%%PYTHON_SITELIBDIR%%/Pymacs/__init__.pyc
X%%PYTHON_SITELIBDIR%%/Pymacs/pymacs.pyo
X%%PYTHON_SITELIBDIR%%/Pymacs/__init__.pyo
X@dirrm %%PYTHON_SITELIBDIR%%/Pymacs/Nn
X@dirrm %%PYTHON_SITELIBDIR%%/Pymacs/Rebox
X@dirrm %%PYTHON_SITELIBDIR%%/Pymacs
END-of-pymacs/pkg-plist
echo x - pymacs/pkg-message
sed 's/^X//' >pymacs/pkg-message << 'END-of-pymacs/pkg-message'
XAdd the following to your emacs initialization file to enable pymacs:
X
X(autoload 'pymacs-load "pymacs" nil t)
X(autoload 'pymacs-eval "pymacs" nil t)
X(autoload 'pymacs-apply "pymacs")
X(autoload 'pymacs-call "pymacs")
X
XSee http://pymacs.progiciels-bpi.ca/manual/index.html for
Xdocumentation on using pymacs.
END-of-pymacs/pkg-message
echo x - pymacs/pkg-descr
sed 's/^X//' >pymacs/pkg-descr << 'END-of-pymacs/pkg-descr'
XPymacs is a powerful tool which, once started from Emacs, allows both-way
Xcommunication between Emacs Lisp and Python.  Pymacs aims Python as an
Xextension language for Emacs rather than the other way around, and this
Xassymetry is reflected in some design choices.  Within Emacs Lisp code, one
Xmay load and use Python modules.  Python functions may themselves use Emacs
Xservices, and handle Emacs Lisp objects kept in Emacs Lisp space.
X
XWWW: http://pymacs.progiciels-bpi.ca/
END-of-pymacs/pkg-descr
echo x - pymacs/distinfo
sed 's/^X//' >pymacs/distinfo << 'END-of-pymacs/distinfo'
XMD5 (Pymacs-0.22.tar.gz) = 73b7a641be100fd90a9be59ecf01fd98
XSIZE (Pymacs-0.22.tar.gz) = 363119
END-of-pymacs/distinfo
echo x - pymacs/Makefile
sed 's/^X//' >pymacs/Makefile << 'END-of-pymacs/Makefile'
X# New ports collection makefile for: pymacs
X# Date created:		23 July 2005
X# Whom:			mwm@mired.org
X#
X# $FreeBSD$
X#
X
XPORTNAME=	Pymacs
XPORTVERSION=	0.22
XCATEGORIES=	devel editors python elisp
XMASTER_SITES=	http://pymacs.progiciels-bpi.ca/archives/
X
XMAINTAINER=	mwm@mired.org
XCOMMENT=	A Python package for scripting emacs
X
XUSE_PYTHON=	yes
XUSE_PYDISTUTILS=yes
XUSE_PYTHON_PREFIX=yes
XUSE_EMACS=	yes
X
X.if !defined(EMACS_PORT_NAME)
XEMACS_PORT_NAME=xemacs21
X.endif
X
X# Install the emacs side of things
Xpost-install:
X	${INSTALL_SCRIPT} ${WRKSRC}/pymacs.el $(LOCALBASE)/${EMACS_SITE_LISPDIR}
X	${EMACS_NAME} -batch -f batch-byte-compile \
X		${LOCALBASE}/${EMACS_SITE_LISPDIR}/pymacs.el
X
X.include <bsd.port.mk>
END-of-pymacs/Makefile
exit





>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050911234220.4941.qmail>