portacle/portacle

A portable common lisp development environment

About Portacle

Portacle is a portable Common Lisp environment. What this means is that it is a fully featured integrated development environment for use with Common Lisp that runs on all major platforms and can even be put onto a USB stick to carry around.

What is this? How do I install it? How do I use it?

For most questions, see the official website. It should give you a good presentation of what this is in detail, how to get set up, and how to use it.

Compiling From Source

In order to build the portacle environment yourself, please refer to the README in the build/ directory of the repository. Note that you usually do not need to do this. The pre-made release packages should be sufficient.

portacle's Issues

Website

All the hip new projects nowadays have a modern and spiffy looking website to attract people like flies to the light.

I don't really care about making this hip or popular, but having something beyond a meagre github README would probably be a good idea.

MacOS High Sierra beta build.

Just FYI it doesn't work on High Sierra (from latests release).
But I've tried to build it by myself and after that it starts working!

Keybind Reference / Emacs Intro

Currently the emacs/config/portacle-help.txt is less than helpful. Needs to be equipped with:

• Emacs terminology
• Emacs keychord notation
• Basic buffer/window/nav chords
• Basic file chords
• Basic cl chords
• How Paredit works and how to use it
• How to customise the Emacs config
• Pointers to further resources on CL and Emacs.

Shared Libraries

In general not shipping shared libraries is a problem, especially on linuxes. Currently the bundle compiled from Ubuntu won't run on Arch for example due to a missing libtinfo.so.5. There's two solutions to that particular problem, first being creating a symlink to libncursesw.so.6 for it, second being to distribute the library with the bundle.

I'm not sure what the smarter decision is here, nor how to automate the process in either case since the dependant libraries of the produced emacs vary depending on the platform. Some kind of inspection and automatic determination process needs to be added to see which libraries can be omitted and which should be shipped.

Furthermore, just shipping dependant libraries can still cause problems if they don't mix well with the overarching OS. That kind of portability issue is probably outside my reach however.

inferior-lisp segfault

Running GNU/Linux, Debian Sid 9.0. Executing portacle/portacle.run results in inferior-lisp the following:

Another interesting thing when you run portacle/portacle.run is the warning message

Warning: arch-dependent data dir '/home/linus/portacle/emacs/lin/libexec/emacs/25.1/x86_64-unknown-linux-gnu/': No such file or directory

First Time Setup

There should be a first-time setup wizard to configure things like git's name and email and such-like.

Fails to start on Fedora 25

Portacle 0.12 won't start on Fedora 25. portacle.desktop shown as Portacle didn't do anything, so I ran the Exec command from within the same directory.

bash -c 'cd $(dirname %k) && ./portacle.run'
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
Warning: arch-dependent data dir '/home/linus/portacle/lin/emacs/libexec/emacs/25.1/x86_64-unknown-linux-gnu/': No such file or directory
Warning: Lisp directory '/home/linus/portacle/lin/emacs/share/emacs/25.1/lisp': No such file or directory
GLib: Cannot convert message: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(emacs:28472): Gtk-WARNING **: Conversion from character set 'ISO-8859-1' to 'UTF-8' is not supported

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(emacs:28472): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

(emacs:28472): GLib-CRITICAL **: g_error_new_literal: assertion 'message != NULL' failed
Fatal error 11: Segmentation fault
Backtrace:
/home/martin/portacle//lin/emacs/bin/emacs[0x4f7742]
/home/martin/portacle//lin/emacs/bin/emacs[0x4df2e9]
/home/martin/portacle//lin/emacs/bin/emacs[0x4f65be]
/home/martin/portacle//lin/emacs/bin/emacs[0x4f67c3]
/home/martin/portacle//lin/emacs/bin/emacs[0x4f67fa]
/home/martin/portacle//lin/lib/libpthread.so.0(+0x10330)[0x7f4ea484b330]
/home/martin/portacle//lin/lib/libgdk_pixbuf-2.0.so.0(+0xa253)[0x7f4ea7096253]
/home/martin/portacle//lin/lib/libgdk_pixbuf-2.0.so.0(gdk_pixbuf_get_formats+0xd)[0x7f4ea709866d]
/home/martin/portacle//lin/lib/libgtk-x11-2.0.so.0(+0xff2dc)[0x7f4ea79d32dc]
/home/martin/portacle//lin/lib/libgobject-2.0.so.0(g_type_create_instance+0x1eb)[0x7f4ea6c2ee3b]
/home/martin/portacle//lin/lib/libgobject-2.0.so.0(+0x15355)[0x7f4ea6c13355]
/home/martin/portacle//lin/lib/libgobject-2.0.so.0(g_object_newv+0x22d)[0x7f4ea6c1510d]
/home/martin/portacle//lin/lib/libgobject-2.0.so.0(g_object_new+0xec)[0x7f4ea6c158bc]
/home/martin/portacle//lin/lib/libgtk-x11-2.0.so.0(gtk_icon_theme_get_for_screen+0x77)[0x7f4ea79d35c7]
/home/martin/portacle//lin/emacs/bin/emacs[0x4d91a5]
/home/martin/portacle//lin/emacs/bin/emacs[0x4da968]
/home/martin/portacle//lin/emacs/bin/emacs[0x4ca9a0]
/home/martin/portacle//lin/emacs/bin/emacs[0x4cb464]
/home/martin/portacle//lin/emacs/bin/emacs[0x550832]
/home/martin/portacle//lin/emacs/bin/emacs[0x583d15]
/home/martin/portacle//lin/emacs/bin/emacs[0x550282]
/home/martin/portacle//lin/emacs/bin/emacs[0x550643]
/home/martin/portacle//lin/emacs/bin/emacs[0x583d15]
/home/martin/portacle//lin/emacs/bin/emacs[0x550643]
/home/martin/portacle//lin/emacs/bin/emacs[0x551b70]
/home/martin/portacle//lin/emacs/bin/emacs[0x55073a]
/home/martin/portacle//lin/emacs/bin/emacs[0x583d15]
/home/martin/portacle//lin/emacs/bin/emacs[0x550643]
/home/martin/portacle//lin/emacs/bin/emacs[0x583d15]
/home/martin/portacle//lin/emacs/bin/emacs[0x550643]
/home/martin/portacle//lin/emacs/bin/emacs[0x583d15]
/home/martin/portacle//lin/emacs/bin/emacs[0x550643]
/home/martin/portacle//lin/emacs/bin/emacs[0x583d15]
/home/martin/portacle//lin/emacs/bin/emacs[0x550643]
/home/martin/portacle//lin/emacs/bin/emacs[0x583d15]
/home/martin/portacle//lin/emacs/bin/emacs[0x54f7f3]
/home/martin/portacle//lin/emacs/bin/emacs[0x54fb3e]
/home/martin/portacle//lin/emacs/bin/emacs[0x553001]
/home/martin/portacle//lin/emacs/bin/emacs[0x54f0dd]
/home/martin/portacle//lin/emacs/bin/emacs[0x4e1ddc]
/home/martin/portacle//lin/emacs/bin/emacs[0x54f08b]
...
./portacle.run: line 7: 28472 Segmentation fault      (core dumped) "$ROOT/lin/launcher/portacle" "$@"
$

MacOS meta key is set to esc instead of option.

MacOS meta key is set to esc instead of option.

Please include the EVIL plugin, too

So that people used to that other editor can more easily try that out, too.

Thanks a lot!

Replace Launcher Scripts

Currently I use a variety of shell wrappers to launch the different parts. This isn't so great due to a variety of reasons, primarily that it requires a bash or cmd from somewhere, which can introduce horrendous library issues as seen in #19.

Instead of this the current portacle.exe C stub that I wrote could be extended to possibly launch any and all parts of the Portacle distribution, and handle the environment in one place. The downside is that it means writing portacle C code.

On Linux, this executable could also always start with wrapped execv* variants to ensure that the system's bash is not invoked under any circumstance except for explicit invoking.

Furthermore: the executable needs to store the LD_LIBRARY_PATH original variable so that it can be restored within environments such as emacs that should not propagate it outside of its own system. Actually, thinking about it, if something is launched through the direct ld-linux.so, I'm not sure if it's necessary to set LD_LIBRARY_PATH at all, so I might just remove that part altogether.

Emacs Crashes with "Memory Exhausted" Under ld-linux.so On Some Systems

This now happens on my Arch system (I know it worked some months ago!) but still doesn't happen on my Mint test system. Very strange.

Convenience Functions for Managing Projects

It'd be great if there were functions to create / rename / clone projects easily. That should take care of a lot of the boilerplate work a user has to do otherwise.

Disable Flyspell on Windows

Since we cannot ship a spellchecker #9 the flyspell mode should not get activated everywhere on Windows in order to avoid confusing warning messages in the minibuffer.

MacOS .dmg doesn't look like usual "drag to install" disk image, fails with "unknown developer"

In my experience, MacOS .dmg's usually present an ISO disk volume with a customized finder window to "drag to install" an Application into the /Applications folder. Alternatively it shows up as one toplevel Application with an icon (and you can see the contents by right-clicking and choosing "Show Package Contents"). The Mac version of Portacle doesn't look like this - it just presents a folder in-place.

Moreover, if I try to launch what appears to be the Portacle executable, I'm getting thwarted by MacOS, telling me "Portable can't be opened because it is from an unidentified developer."

We can possibly help with this (our organization does have a Mac Developer ID certificate), but I'm not sure if the Portacle project would want our organization's certificate on the distribution, and I'm not sure what the intended packaging is supposed to look like.

We have been distributing something like Portacle but with pre-built images of Gendl (an open-source KBE system built on CL) rather than vanilla CL.

Portacle might make for a smoother and more standardized way for us to distribute these "convenience" Gendl builds, or at least as a basis for doing that, but I'll have to understand more about how the packaging is expected to be. Also, we are distributing with CCL as the included CL engine. Has the Portacle project considered including more than one CL engine by default?

Ship Aspell

Currently aspell is missing from the distribution. We should include it as well so that flyspell is guaranteed to work.

Ship GIT

Git is an essential tool for modern development and shipping it (+magit) sounds like a jolly idea to me. Depending on how much needs to be included to sport that though I might reconsider this.

simple typo in help file

On line 59 of the help file, "scratch" should be changed to "repl".

The current text is obviously wrong:

  C-x b *scratch* RET

This means the following: Hold Control pressed and press x. Release both. Press b and release it. Type "repl". Press Return.

Problems opening in macOS

When I try to open portacle it does not open. However if I go to the contents of the package:
Portacle.app/Contents/MacOS/portacle
And run it: The application runs opening a terminal and showing this errors:
Warning: arch-dependent data dir '/Users/linus/portacle/mac/emacs/libexec/emacs/25.1/x86_64-apple-darwin16.5.0/': No such file or directory

Warning: Lisp directory '/Users/linus/portacle/mac/emacs/share/emacs/25.1/lisp': No such file or directory

Clearly my user is not "linus". Is there a file in which I can configure this?
Thanks

Release console after start on Windows

When one run portacle.exe from cmd or other console program (say, Far manager), program does not release console window until exit from Emacs, leading to unnecessary console window in task bar.

Error running hunspell

On a vanilla OSX Sierra set up with no homebrew etc there is no libintl (from gettext) in /usr/local/opt/lib. This is needed by hunspell which is used by flyspell. It's easy enough to install the library using the usual curl, make, make install routine, but if the purpose is an out of the box Dr. Racket like experience then it would be good to include that library in Portacle.

Ship a Standard Font

Fonts are another portability problem, so it would be good to ship a default one.

OS X App Translocation

Problem
Clicking the Portacle.app file does nothing. The release directory was extracted via tar -xvzf and I navigate to the expanded directory from Finder to click the .app file.
I'm running Sierra (10.12.2).

Troubleshooting
I checked syslog and saw

com.apple.xpc.launchd[1] (org.shirakumo.portacle.1808[14129]) <Warning>: Service exited with abnormal code: 127

I also navigated to the Portacle.app and tried to run portacle.sh directly to see what would happen and got an error about a missing symbol from a library (posted below). I'm not sure if it's related or not.

dyld: Symbol not found: _iconv
  Referenced from: /usr/lib/libcups.2.dylib
  Expected in: /Users/dev/portacle//usr/mac/lib//libiconv.2.dylib
 in /usr/lib/libcups.2.dylib
/Users/dev/portacle//emacs/mac/emacs.sh: line 51: 14790 Abort trap: 6           "$SCRIPT/bin/emacs" --name Portacle -T Portacle -q -l "$ROOT/config/emacs-init.el" "$@"

Magit Error "Nothing staged" on Win7

After staging some changes and trying to commit, I get the message user-error: Nothing staged (or unstaged). Committing the same staged changes via command line using a locally installed git worked just fine.

Portacle 0.11 on Win7, updating all packages didn't help.

SBCL logo missing on Portacle's website

https://shinmera.github.io/portacle/sbcl.svg -- this picture seems to be missing.

Does not start on Xubuntu 16.04 (and probably all Ubuntu flavors)

Cloned your repo into my home directory (home/stack/)

• gui click on portacle.desktop as advised does nothing;
• executing ./portacle.run in /home/stack/portacle/ results in:

/home/stack/portacle//emacs/lin/emacs.sh: line 47: /home/stack/portacle//usr/lib/ld-linux.so: No such file or directory

P.S. I was away the last time I brought up this issue with 14.04 - sorry. I am monitoring notifications and will be happy to assist you in debugging this if you are so inclined.

Mode to Set "Standard" Keybindings

It might be useful to allow users to configure a custom keyboard mode that sets "standard" keybindings for copy/paste/undo/redo/save/open/find. Though I'll have to think on how to mitigate the keybindings we'll have to replace by this.

Add a Way to Automatically Upgrade

There's a command to automatically pull new sources, but that doesn't update the binary parts. It should be possible to easily move on to the next release without losing all your projects and configurations or having to do it manually yourself.

(CFFI::FL-ERROR "Unable to load foreign library (~A).~% ~A" GLIB::GLIB "Error opening shared object \"libglib-2.0-0.dll\": ..)

I tried the following:
(ql:quickload "cl-cffi-gtk")

Trying:

cffi:*foreign-library-directories*
Nil

I'm not sure if quicklisp or Portacle is having the problem; I believe you can get around it by setting up the FFI library path relative to Portacle root dir, but I haven't tried it yet (first time I've really tried CL is Portacle! It's amazing!)

Mac OS version

"You can’t use this version of the application ..." error when launching portacle. It says it needs 10.12. I've only noticed since I have El Capitan on my laptop and Sierra on desktop. Is this really necessary? If not, it could be solved by using a gcc flag -mmacosx-version-min=10.7 (10.7 is reasonable enough, no?).

Petit freeze in REPL

Petit freeze occurs when company-mode completion candidates pop-up in REPL.
This problem does not occur when company-quickhelp-mode is disabled or company-quickhelp-delay variable has bigger value such 1.0.

Build Scripts Don't Exit on Error

Emacs provided in lin64-portacle-0.0.3.tar.xz is linked against libgnutls.so.26, thus fails to launch on environments with libgnutls.so.28 instead. The user has to build emacs themselves on their local machine, making sure to install all the dependencies by hand.

Thankfully after installing them the build/emacs.sh works marvelously and Portacle will operate properly.

When attempting to build with build/all.sh without the dependencies installed however, the errors on failure to build emacs end up far up the process output and the user has to scroll up drastically to find the error messages.

Add The Silver Searcher / ag

Having a fast searcher to look through sources and stuff is generally useful.

Autocompletion Emacs

Auto completion does not work in lisp source buffers

Clean Up Referenced Repository In Deployment Target

Currently a deployed target will use the same directory structure as a build host, and will also include the same git repository. This is not optimal as it leads to a lot of unnecessary files being potentially pulled in when a user wants to update. The only relevant parts for them are the config/ directory.

This can be worked around in one of two ways:

1. Use a sparse clone that is set up automatically during packaging. Sparse clones are described here
2. Split off the configuration files into a separate repository entirely, potentially along with a fork of my .emacs. This would allow cleaning it out and only including Portacle relevant parts, as well as making it potentially diverge from my own preferences.

I'll have to see what I want to do.

Win64 - Spaces on install path

If Portacle is installed under a path with spaces in it, f.e. C:\Program Files\portacle, launching portacle.exe will fail.

MacOS options do not persist after closing the app.

MacOS options do not persist after closing the app. (i.e. changing the theme or font size)

Ship ASDF

Sometimes the ASDF bundled in SBCL is pretty out of date. Would be better if we could ship a manually built ASDF.

Gtk "atk-bridge" failed to load: libunity-gtk-module.so: undefined symbol: g_type_check_instance_is_fundamentally_a

On Ubuntu 16.10 I get:

➜  portacle git:(master) ✗ ./portacle.run 
Warning: arch-dependent data dir '/home/linus/portacle/emacs/lin/libexec/emacs/25.1/x86_64-unknown-linux-gnu/': No such file or directory
Gtk-Message: Failed to load module "atk-bridge"
/home/mac/Desktop/portacle/emacs/lin/bin/emacs: symbol lookup error: /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libunity-gtk-module.so: undefined symbol: g_type_check_instance_is_fundamentally_a

Include Hunspell for Win7

As spell checking is already part of portacle's configuration, I suggest to include Hunspell for Win users. Not having the means to build it myself, I fetched mine from https://sourceforge.net/projects/ezwinports/files/hunspell-1.3.2-3-w32-bin.zip which works fine.

Change ASDF to Use FASL Paths Relative to Portacle If Possible

Currently ASDF always uses the absolute path of the filesystem, which can result in ridiculously long paths in the cache directory. It also means that FASLs get remade when Portacle is moved, despite it probably not being necessary to do so.

Win10 default SLIME location does not respect installation path

Today I tried using Portacle on friend's Windows PC. He didn't have any space on his main partition(?), so we installed it in other directory (P: drive). After installing, we successfully ran the Emacs; however, we encountered a problem during starting the SLIME - the path .slime could not be created. This was due to the lack of empty space, but SLIME tried to create its files on J:, when it was installed on P: and should - in my opinion - install everything there.

Fails on linux ubuntu 14.04

clicking on .desktop file does not do anything (visible)
executing portacle.run fails:
xxx/portacle/emacs/lin/emacs.sh: line 46: xxx/portacle/emacs/lin/bin/emacs: No such file or directory

(anonymizing my directory structure with xxx)

GIT_ASKPASS not available on Win7

Just upgraded to the latest portacle (still 0.11) on my work box. Assuming your fix of portacle-launcher works since I did not get this far before...

git: 'credential-wincred' is not a git command. See 'git --help'.
error: cannot spawn git-gui--askpass: No such file or directory
bash.exe: warning: could not find /tmp, please create!
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Password for 'https://[email protected]': No error

Wincred is not found, which in itself would be a minor inconvenience only. Unfortunately there does not seem to be a git-gui included, so that my setting of (setenv "GIT_ASKPASS" "git-gui--askpass") does not work here. Have you got any suggestion how I may be able to enter my git repository password?

portacle fails on Windows 10 Enterprise 2016 LTSB

Download of latest build from official homesite fails during install step with:

"Portacle Installer: error

Non 7z archive."

The homepage mentions "After extraction", but the downloaded files is and exe and most recent 64-bit 7z fails to extract it anyway.

This happens both before and after I've installed 7-zip. This happens after the prompt asking for installation base have been shown.

I can't test on other versions of Windows, so I have no input regarding how widespread the issue could be, but I have seen other mentions of USB installers/installs failing on Windows 10. My current windows10 install is less than a week old.

Better Installation Instructions

Especially on Windows 8+ complications arise when the program is installed into the Program Files directory, as Windows will, as it is, deny the program the ability to create new files and folders within it, making SBCL unable to launch and populate its ASDF cache directory.

Thus, better installation instructions are needed that note that the program will need to have write access to its folders.

This is NOT an issue - not sure where to leave a note of Thanks.

This is a great package and makes Lisp very accessible! Thanks to everyone who worked on this.

Swank FASL Location

Currently swank still stores its fasls in the user directory, which means it leaks.

Suggestions for OSX Portacle

First, this is a really commendable project and I hope it would encourage people to try common lisp. I know I can now ask my son to try out common lisp one he's done with SICP/racket.

I installed it today on a fresh macbook air (2015) and the instructions worked great. I was looking through the help page and noticed C-left C-right and C-up, C-down for slurping/barfing/convoluting. These are trapped by OSX but the C-{} C-() M-up down bindings work.

Also, maybe a suggestion somewhere to OSX users that they might find making command key Meta, in Emacs, more ergonomic:
(when (eq 'darwin system-type) (setq mac-command-modifier 'meta))
On a similar line a suggestion to all users that they switch caps lock and control key in settings for ergonomic reasons.

ASLR Leads to Emacs Crash on Build

Hi, I'm getting a segfault when building emacs from portacle. Didn't took time to investigate. On Debian unstable, gcc (Debian 6.3.0-13) 6.3.0 20170415

make -C lib all
[...]
Loading /home/xs/brx/portacle/build/emacs/lisp/tooltip.el (source)...
Finding pointers to doc strings...
Finding pointers to doc strings...done
Dumping under the name emacs
Makefile:736: recipe for target 'bootstrap-emacs' failed
make[1]: *** [bootstrap-emacs] Segmentation fault
make[1]: Leaving directory '/home/xs/brx/portacle/build/emacs/src'
Makefile:398: recipe for target 'src' failed
make: *** [src] Error 2

Broken link to OSX download

Page https://shinmera.github.io/portacle/ contains broken link to OSX release:

https://github.com/Shinmera/portacle/releases/download/0.11/mac-portacle.tar.xz

This link is in two places – header and text.

Correct link is:

https://github.com/Shinmera/portacle/releases/download/0.11/mac-portacle.dmg