> On Friday 21 March 2014 14:07:23 you wrote:
>> thanks for the updated infos.
>> In the future, would you post a quick changelog to the list when the
>> svn is updated, or is there another way to be automatically informed
>> when something new has been submited to the repository ?
>
> Hmm... not
On Friday 21 March 2014 14:07:23 you wrote:
> thanks for the updated infos.
> In the future, would you post a quick changelog to the list when the
> svn is updated, or is there another way to be automatically informed
> when something new has been submited to the repository ?
Hmm... not sure about
> I made some progress, my planned basic features are roughly done, but I had so
> far no time to finish it up. There are still some minor issues to be solved.
> But right now I have no time for spare time projects.
sure, i let you do it at your speed as i can not contribute to the
code, but only
On Friday 21 March 2014 10:52:41 Raphaël Mouneyres wrote:
> hello,
>
> i've been using the LSCP shell yesterday, and it has been of a great
> help, especially the command history.
The LSCP shell is still work in progress.
I made some progress, my planned basic features are roughly done, but I ha
hello,
i've been using the LSCP shell yesterday, and it has been of a great
help, especially the command history.
I had previously mentioned some enhancements, and i confirm they would
be great to have
>when you're in a command history, you have to use the delete key, you cannot
>use the left ar
On Saturday 08 February 2014 18:46:02 raf wrote:
> some enhancement for the future ?
> after you've gone into command history with the up arrow, you cannot come
> back to a blank line when you're in a command history, you have to use the
> delete key, you cannot use the left arrow to change some pa
> On Saturday 08 February 2014 15:23:17 raf wrote:
>> the sampler engine is running ok, but strangely the lscp shell complains
>> that the engine is too old, although they have just been compiled together
>> from the latest svn version...
>>
>> LinuxSampler 1.0.0.svn23
>
> That version is from 20
On Saturday 08 February 2014 15:23:17 raf wrote:
> the sampler engine is running ok, but strangely the lscp shell complains
> that the engine is too old, although they have just been compiled together
> from the latest svn version...
>
> LinuxSampler 1.0.0.svn23
That version is from 2013 by the w
On Saturday 08 February 2014 15:23:17 you wrote:
> the sampler engine is running ok, but strangely the lscp shell complains
> that the engine is too old, although they have just been compiled together
> from the latest svn version...
>
> LinuxSampler 1.0.0.svn23
>
> [seijitsu@astrux ~]$ lscp
> LS
Excellent, compiles fine without errors (some warnings about deprecated midi
functions)
the sampler engine is running ok, but strangely the lscp shell complains that
the engine is too old, although they have just been compiled together from the
latest svn version...
LinuxSampler 1.0.0.svn23
[
On Friday 07 February 2014 17:19:07 Christian Schoenebeck wrote:
> > my version was 3.0.1, I updated to
> > [seijitsu@astrux linuxsampler-svn]$ bison -V
> > bison (GNU Bison) 3.0.2
> > Written by Robert Corbett and Richard Stallman.
> >
> > but still got the same error.
>
> Yeah, I just tested it
On Sat, February 8, 2014 3:07 am, Christian Schoenebeck wrote:
> On Friday 07 February 2014 17:25:27 Patrick Shirkey wrote:
>> On Sat, February 8, 2014 1:01 am, Christian Schoenebeck wrote:
>> > On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote:
>> >> It compiles fine for me on debian-7.0
On Friday 07 February 2014 00:25:35 raf wrote:
> i don't know anything about bison... i wouldn't be of any help to track
> down the problem.
>
> my version was 3.0.1, I updated to
> [seijitsu@astrux linuxsampler-svn]$ bison -V
> bison (GNU Bison) 3.0.2
> Written by Robert Corbett and Richard Stall
On Friday 07 February 2014 17:25:27 Patrick Shirkey wrote:
> On Sat, February 8, 2014 1:01 am, Christian Schoenebeck wrote:
> > On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote:
> >> It compiles fine for me on debian-7.0 64bit. However it crashes on start
> >
> >> and I get this backtrace
On Sat, February 8, 2014 1:01 am, Christian Schoenebeck wrote:
> On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote:
>> It compiles fine for me on debian-7.0 64bit. However it crashes on start
>> and I get this backtrace:
>
> Does the attached patch fix it?
>
Moves it slightly but looks t
On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote:
> It compiles fine for me on debian-7.0 64bit. However it crashes on start
> and I get this backtrace:
Does the attached patch fix it?
CU
Christian
Index: src/shell/TerminalCtrl.cpp
On Fri, February 7, 2014 7:41 am, Christian Schoenebeck wrote:
> Ok, I just committed an initial version of the LSCP shell to SVN. The
> application is just called "lscp". There is also a man page.
>
> I decided to go the thin-client route, that is LSCP aware stuff being
> handled
> on sampler sid
Le 6 févr. 2014 à 22:37, Christian Schoenebeck a écrit :
> On Thursday 06 February 2014 23:23:29 raf wrote:
>> after updating the svn repos (libgig-svn just in case and
>> linuxsampler-svn), it fails compiling on lscp.y any idea ? strangely i
>> found the very same function in lscpparser.cpp
>>
On Thursday 06 February 2014 23:23:29 raf wrote:
> after updating the svn repos (libgig-svn just in case and
> linuxsampler-svn), it fails compiling on lscp.y any idea ? strangely i
> found the very same function in lscpparser.cpp
>
[snip]
> lscpparser.cpp -fPIC -DPIC -o .libs/lscpparser.o lscp.y
You're awesome, i jumped straight to the shell !
after updating the svn repos (libgig-svn just in case and linuxsampler-svn), it
fails compiling on lscp.y
any idea ? strangely i found the very same function in lscpparser.cpp
make[3]: Entering directory
'/home/seijitsu/build/linuxsampler-svn/src
Ok, I just committed an initial version of the LSCP shell to SVN. The
application is just called "lscp". There is also a man page.
I decided to go the thin-client route, that is LSCP aware stuff being handled
on sampler side, and the shell application is more or less just forwarding
individual
>
> Hello! I'm really happy about this idea! Almost everything I do with
> LinuxSampler is directly through the commandline, as at present I can't
> really use the current front-ends. Thank you for this consideration.
>
> Kevin
>
---
On Fri, January 31, 2014 5:27 am, Christian Schoenebeck wrote:
> Hi!
>
> I planned to write a shell command line application for LSCP. For this I
> already played around with Bison's auto generated parser tables. As a
> first
> result of these experiments, the sampler is now providing more useful
Hi!
I planned to write a shell command line application for LSCP. For this I
already played around with Bison's auto generated parser tables. As a first
result of these experiments, the sampler is now providing more useful error
messages on LSCP syntax errors. Before, if you i.e. sent "GET S" (
24 matches
Mail list logo
