Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 01:08

    pmoura on master

    Fix spurious messages at loadin… (compare)

  • 01:02

    pmoura on master

    Update `os` library support for… (compare)

  • Nov 27 22:04

    pmoura on master

    Add instructions on how to prov… (compare)

  • Nov 26 22:10

    pmoura on master

    Fix `debugger` tool to call the… (compare)

  • Nov 26 19:15

    pmoura on master

    Fix using a overriding meta-pre… (compare)

  • Nov 26 00:28

    pmoura on master

    Additional test for the de fact… (compare)

  • Nov 24 23:50

    pmoura on master

    Update Trealla ProLog adapter a… (compare)

  • Nov 24 22:28

    pmoura on master

    Add Trealla ProLog support to t… (compare)

  • Nov 24 18:15

    pmoura on master

    Unmark LVM support as experimen… (compare)

  • Nov 24 14:31

    pmoura on master

    Update `os` library support for… (compare)

  • Nov 24 13:57

    pmoura on master

    Update `random` library support… (compare)

  • Nov 24 12:10

    pmoura on master

    Fix `random` library support fo… (compare)

  • Nov 24 11:57

    pmoura on master

    Fix some typos in the new `os` … (compare)

  • Nov 24 11:13

    pmoura on master

    Add experimental support for Tr… (compare)

  • Nov 23 19:30

    pmoura on master

    Additional tests for the de fac… (compare)

  • Nov 23 19:10

    pmoura on master

    Additional tests for the `at_en… (compare)

  • Nov 23 13:27

    pmoura on master

    Update `tplgt` integration scri… (compare)

  • Nov 23 12:24

    pmoura on master

    Update `tplgt` integration scri… (compare)

  • Nov 22 18:36

    pmoura on master

    List the experimental integrati… (compare)

  • Nov 22 18:34

    pmoura on master

    Fix comment typo in the `logtal… (compare)

Paulo Moura
@pmoura
LVM is not (currently) a public Prolog system. That's all I can say for now.
YungTse Technology
@YungTseTech_twitter
So far I've only traced it to a professor in Guelph. Is that the one?
YungTse Technology
@YungTseTech_twitter
Definition of madness: getting the urge to see if Logtalk can be made to work with trealla. :D
Paulo Moura
@pmoura
Possibly. There are still missing standard predicates that are required. Also, apparently, operator parsing bugs.
Paulo Moura
@pmoura
You cam follow progress here: infradig/trealla#99
Paul Brown
@PaulBrownMagic
When deploying swilgt applications is using SWI's pack_install(logtalk) the recommended way to go about it? Or is installing logtalk onto the system in the usual way better?
Paulo Moura
@pmoura
That pack was specifically created for deploying Logtalk applocations when using SWI-Prolog as the backend (although I'm unable to stop people from using it for development despite all the warnigs that's not its purpose).
Paul Brown
@PaulBrownMagic
Yes,
and I'm needing to deploy my PhD application, finally!
So just wondering if it's better to use that, or install logtalk onto the server in the usual way
Paulo Moura
@pmoura
👍
The pack can simplify deplyoment in the sense that you only run the SWI-Prolog installer and then install Logtalk from within a SWI-Prolog session.
That's fine, of course, assuming that the implicit directory structure for packs works for the deployed application.
Paul Brown
@PaulBrownMagic
Alright, I think I'll install logtalk in the usual way then so I get more control
as in, easier control!
Paulo Moura
@pmoura
The Logtalk installers usally allows you to get the files that you may want to modify in a more accessible directory. The packs directory is deep and hidden.
Paul Brown
@PaulBrownMagic
exactly, and I need to setup my "third-party" libs in settings.lgt
Paulo Moura
@pmoura
Well, the settings.lgt file do work independently of the way you install Logtalk...
Paul Brown
@PaulBrownMagic
Alright, well I used the .deb to install it, it's working, and running surprisingly fast!
Paul Brown
@PaulBrownMagic
Running with systemd... just got to point nginx at it...
Paul Brown
@PaulBrownMagic
And running!
YungTse Technology
@YungTseTech_twitter
@pmoura I really like infradig's style. He's a repairing machine!
Paulo Moura
@pmoura
Yes :-)
YungTse Technology
@YungTseTech_twitter
Reminds me of you in some ways. Has a crazy idea, works like mad to get that crazy idea alive, then works like made to improve it at every opportunity. :D
My crazy idea is two-fold.
First, I want TPL on (higher-end) bare metal MCUs.
Second I want a tiling window manager that's configured/programmed via Logtalk, and tpl fits the bill for size there.
Paulo Moura
@pmoura
I'm hopeful that the next Logtalk stable release will include full support for Trealla Prolog, even if experimental.
YungTse Technology
@YungTseTech_twitter
I'll be there to test it out then. I'm intrigued by trealla.
Putting it into bare metal is a bit of a problem at this point -- loads of assumed infrastructure has to be replicated and/or stubbed out.
And with six-day work weeks I just lack the time and energy to devote properly to it. :-/
Paulo Moura
@pmoura
Easy: (1) clone yourself (2) send your clone to work while you stay home playing with Logtalk (3) there's no step (3).
YungTse Technology
@YungTseTech_twitter
That's obviously your solution to Logtalk and workload! :D
Paul Brown
@PaulBrownMagic
bspwm is a tiling window manager that can be configured in Logtalk
How do you configure it using Logtalk? Where are the juicy details? 😀
Paul Brown
@PaulBrownMagic
Well it needs bspwmrc to be an executable, and it doesn't care what language it's in so long as you can ./bspwmrc. Then all the configurations are made with shell calls, so if I want to set a border width I can just type into my shell: bspc config border_width 2, or in logtalk os::shell('bspc config border_width 2').
But you don't really need much logic in your base configuration. You really use it more with hotkeys, and bspwm is usually used with sxhkd to handle that, which takes a command to associate with a key combo, for example alt + ctrl + {h, j, k, l} logtalk -s $HOME/sxhkd/loader.lgt -g "tiling::select_dir({h, j, k, l})" could work, but I don't think you'll want to wait for logtalk to load for each keystroke...
Paul Brown
@PaulBrownMagic
So lot's of potential, but it's hard to justify the extra layer of using Logtalk, except bspwm doesn't handle multiple monitors in a nice way, so some kind of Logtalk daemon service to communicate with there could be very nice.
I run it, and I'm almost happy with my dual monitor setup, but my clever scripts are in python; simple ones in bash.
YungTse Technology
@YungTseTech_twitter
That ... is perverse.
Paulo Moura
@pmoura
For that kind of uses, the best option is likely to generate an executable that embbeds the Logtalk code using GNU Prolog. Then running the executable should be quite fast.
Paul Brown
@PaulBrownMagic
I've yet to manage to get GNU Prolog to compile anything
Paulo Moura
@pmoura
Hum? What error did you get?
Paul Brown
@PaulBrownMagic
The not "understanding the manual" error! I only looked over it briefly and it wasn't obvious...
Paulo Moura
@pmoura
See logtalk3/scripts/embedding/gprolog.
Also logtalk3/scripts/embedding/SCRIPT.txt.
Paul Brown
@PaulBrownMagic
Love it when there's an example! I'll have a look.
Paulo Moura
@pmoura
👍