Thanks, done. On Sat, May 30, 2015, 12:03 <[email protected]> wrote:
> [email protected] > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/luvit/topics> > Google > Groups > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > Topic digest > View all topics > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/luvit/topics> > > - pointing lit at a custom directory > <#msg-f:1502588678208839281_group_thread_0> - 5 Updates > > pointing lit at a custom directory > <http://groups.google.com/group/luvit/t/167a3c853c1b6c06?utm_source=digest&utm_medium=email> > Martin Croome <[email protected]>: May 29 08:58AM -0700 > > Hi. I'm (ab)using lit for a specific task where I need it to behave in a > slightly different way. This means that I have to require db and core > rather than pass via autocore. Is there any way to do this without > creating > my own version of the lit package? > > Thanks > Tim Caswell <[email protected]>: May 29 11:57AM -0500 > > You can customize the litconfig to use via environment variables and you > can customize where the database on disk is via the config file. But if > you want to change the behavior of lit itself beyond this you'll need to > build a custom lit. > > Luckilly this is trivially easy. Also note that you can use luvi to run > your custom lit without having to constantly rebuild the binary. > > luvi path/to/custom/lit -- lit arguments > > > > On Fri, May 29, 2015 at 10:58 AM, Martin Croome <[email protected]> > wrote: > > Tim Caswell <[email protected]>: May 29 11:58AM -0500 > > Also lit is available as a lit package you can depend on and use the code > from your app as a library. The default exports is autocore, but there is > nothing stopping you from reaching in and grabbing stuff directly. > > Martin Croome <[email protected]>: May 29 12:47PM -0700 > > Hi Tim > > That is really what I was asking. I'm already embedding it but I need to > pick up core, db and vfs to do what I need to do. I tried to require them > directly (lit/core, lit/libs/core and ./deps/lit/libs/core) but didn't > seem > to manage it. It always seemed to pickup autocore for some reason. Need to > study the require code to figure it out. > > Currently I just use my own init.lua but I'd prefer not to. > > Martin > > On Friday, May 29, 2015 at 6:58:20 PM UTC+2, Tim Caswell wrote: > Tim Caswell <[email protected]>: May 29 10:03PM -0500 > > Ahh. I wasn't careful to make everything in the libs folder work without > pulling in autocore. I'm open to ideas for ways to make the core libraries > easier to use as libraries. Feel free to open an issue describing what you > need broken out. Knowing you use case or at least requirements will help a > ton in knowing where to refactor lit core. > > -----Original Message----- > From: "Martin Croome" <[email protected]> > Sent: 5/29/2015 2:47 PM > To: "[email protected]" <[email protected]> > Subject: Re: pointing lit at a custom directory > > Hi Tim > > > That is really what I was asking. I'm already embedding it but I need to > pick up core, db and vfs to do what I need to do. I tried to require them > directly (lit/core, lit/libs/core and ./deps/lit/libs/core) but didn't seem > to manage it. It always seemed to pickup autocore for some reason. Need to > study the require code to figure it out. > > > Currently I just use my own init.lua but I'd prefer not to. > > > Martin > > On Friday, May 29, 2015 at 6:58:20 PM UTC+2, Tim Caswell wrote: > Also lit is available as a lit package you can depend on and use the code > from your app as a library. The default exports is autocore, but there is > nothing stopping you from reaching in and grabbing stuff directly. > > > > On Fri, May 29, 2015 at 11:57 AM, Tim Caswell <[email protected]> wrote: > > You can customize the litconfig to use via environment variables and you > can customize where the database on disk is via the config file. But if you > want to change the behavior of lit itself beyond this you'll need to build > a custom lit. > > > Luckilly this is trivially easy. Also note that you can use luvi to run > your custom lit without having to constantly rebuild the binary. > > > luvi path/to/custom/lit -- lit arguments > > > > > > On Fri, May 29, 2015 at 10:58 AM, Martin Croome <[email protected]> > wrote: > > Hi. I'm (ab)using lit for a specific task where I need it to behave in a > slightly different way. This means that I have to require db and core > rather than pass via autocore. Is there any way to do this without creating > my own version of the lit package? > > > Thanks > -- > You received this message because you are subscribed to the Google Groups > "luvit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "luvit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > Back to top <#msg-f:1502588678208839281_digest_top> > You received this digest because you're subscribed to updates for this > group. You can change your settings on the group membership page > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/luvit/join> > . > To unsubscribe from this group and stop receiving emails from it send an > email to [email protected]. > -- You received this message because you are subscribed to the Google Groups "luvit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
