Re: How do I turn ANSI-terminal colourising off?

Feliks Kluzniak <[email protected]> wrote:Jan,

I appreciate your response, but I am not quite sure I understand.  The "Yes" is followed by information that does not necessarily support it. ;-)

My interpretation of what you wrote:

1. The new app is stand-alone, and is quite wonderful, but one must use the app's special terminal window.

No. The app also contains the swipl binary.

2. If, for some reason, one doesn't want to use the special terminal window, one still has the option of using MacPorts, which will be kept more or less up-to-date.

If the app works fine, there will be no more macports binary on www.swi-prolog.org.  As long as Paulo or someone else submits new
Portfiles, port install should still work. There is also brew and just compiling the sources isn't too hard either.  Finally, Macports
Is in fact still used to create the binaries that go into the app.

Is that correct?


What I am really afraid of is a scenario in which one is more or less forced to use the special terminal window to get advantage of future releases: wonderful as that special window will be, it will not always suit everybody's needs.

To give a concrete example: I am addicted to running programs in Emacs shell mode, and would like to be able to continue doing just that.

Thanks,
-- Feliks



On Aug 16, 2013, at 22:41, Jan Wielemaker <[email protected]> wrote:

> Hi Feliks,
> 
> On 08/16/2013 10:10 PM, Feliks Kluzniak wrote:
>> Hi Jan,
>> 
>>> Soon, the terminal based SWI-Prolog will be mostly for server and
>>> scripting applications.  Carlo's Qt base console will be the
>>> default interaction console on all platforms.  With some luck,
>>> there will be a real Mac App that can be run from the dmg file, be
>>> installed anywhere and opens a nice window :-)
>> 
>> I use a Mac, and this sounds a little alarming.
>> 
>> I hope it will always be really, really easy to use just the
>> old-style command line interface (in whatever window I like to run my
>> shell in).
> 
> Yes.  In fact, we get rid of dependencies on Macports and conflicts that
> I have been warned about for some time: installing the binary at it is
> now distributed installs things in Macports.  If you have no Macports,
> that is fine, but if you have it or later decide to install it, the
> macports admin is upset by files that come from an unknown source.
> 
> The app is self-contained and only depends on X11 as non-standard
> Mac feature.  You can install it anywhere and all you need to do
> is add <app>/Contents/MacOS to your $PATH to run the good old
> commands.  The new command swipl-win gives the new console.
> 
> The new windowed app is not that much different from what you are
> used to.  It is basically just a terminal.  There are only a few
> nice extras:
> 
>  - It has a menu bar that makes getting started a little easier.
>    Not only that, but is also allows controlling Prolog while it
>    is crunching away.  For example, the "Debug/Threads minitor"
>    will show CPU and memory usage in a graph.  Quite handy if
>    you wonder what your program is doing.
>  - You can extend the menu bar with your own stuff (for example
>    with additional menus for your application).
>  - Warnings and errors in the console that are related to a
>    file are clickable, which opens the editor at the error
>    location.
>  - You can open additional consoles in the same engine (they
>    run in their own thread).  That too is nice if you want to
>    query the DB while your main task is crunching.
>  - You can double-click a .pl/.prolog file from the finder to
>    open an instance with this file loaded.
> 
> Cheers --- Jan

-------------- next part --------------
HTML attachment scrubbed and removed
_______________________________________________
SWI-Prolog mailing list
[email protected]
https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog