Re: [code] Your uses of Textadept?

From: Robert Gieseke <rob.g.att.web.de>
Date: Tue, 5 Jan 2016 21:36:31 +0100

Richard,

thanks a lot for your detailed answer! That's quite cool to hear
Textadept being used so extensively extended :-)
Also interesting that continuous integration with the Nightlies seems to
be easier than Long-Term-Support releases ...

Cheers,
Robert

Am 05/01/16 um 14:42 schrieb Richard Philips:
> Hello Robert,
>
>
> Our team is split over two locations: the first team (Anet) are employed by
> the University of Antwerp and consists of 12 people. Ten of them use
> Textadept regularly (5 of them are developers, the others write reST
> documentation, tutorials (also reST), translations, CSS, parametrisation
> (all in Textadept) etc.
>
> The second team is a company (Ciblis, a spin-off, we are shareholders)
> which commercializes our (Library) application. They have also 5 developers
> who are using Textadept every minute of their life :-)
>
> We developed a package (62 Lua scripts) which enhances Textadept to a full
> blown IDE. This is quite remarkable because our software is completely web
> based. People develop (or write documentation), with perfect support for
> the programming language they are using. Then CTRL+L + CTRL+Q sends their
> work to a remote server (over SSH) where it is automatically installed,
> parsed, checked on style guide, etc, and immediately available for testing.
>
> That package contains also some python scripts used in maintaining
> Textadept. We have no house rules on what platform people should develop
> or what tools they should use. But I notice that everyone uses Textadept :-)
> So I see everyone has about the same procedure: they arrive in the morning,
> they fire up their workstation, they run python download.py (one of those
> python scripts). That script fetches the nightly built, installs it on the
> workstation, updates our own Lua scripts.
>
> It is a tribute to the careful way Mitchell develops Textadept that their
> is almost never a regression. The API is fairly stable. When there goes
> something wrong - but I repeat: almost never - we can easily go back to the
> working situation.
>
> By always working with the nightly built, we know what is going on with
> Textadept: I also read the mailing list archives and during coffee break we
> inform each other on what is new.
>
> I think Mitchell wil forgive me if I say that Textadept is a 'primitive'
> tool (like every programmer's editor is). But I like it this way: its
> elegance together with the power of Lua makes sure that the
> 'administrative' things of software development are reduced to a minimum
> while our developers remain knowledgeable to the things happening behind
> the curtains.
>
>
> Richard
>
>
>
>
> On Tuesday, January 5, 2016, Robert Gieseke <rob.g.att.web.de> wrote:
>
>> Hi Richard,
>>
>> can you maybe give some examples on how Textadept helps in your
>> workflows (just curious) and another question, how many people are using
>> Textadept and how do you manage updates in your library?
>>
>> I do recommend Textadept to friends and help them write some short cuts,
>> but when they ask me the next time, one year later, Textadept usually
>> has moved on a bit ...
>>
>> Cheers,
>> Robert
>>
>> Am 03/01/16 um 12:16 schrieb Richard Philips:
>>> Hi,
>>>
>>>
>>> I develop library automation software for a living. Our software base
>>> counts more than 11000 text files, together more than 300Mb code.
>>>
>>> Our developers work on different platforms: mostly Windows (7, 8, 10) but
>>> also OSX and Ubuntu. We program in several languages: Python, M, PHP,
>>> Javascript and (recently) Elixir. Our documentation platform is Sphinx.
>> So
>>> we write a lot of reStructuredText.
>>>
>>> Until a few year ago, our main text editor was Emacs. We developed a
>> number
>>> of Elisp routines to help us in our programming work.
>>>
>>> Then we discovered Textadept: its sober aesthetics appealed to us. We
>> wrote
>>> more than 60 Lua scripts to help us out in our daily work. These days
>> those
>>> 11000 text files are all maintained by Textadept.
>>>
>>> The scripts we wrote, are mainly syntax files for specialized formats
>> which
>>> are of no use to the larger community.
>>>
>>> Nevertheless we like to support Textadept. We do that by sponsoring
>>> Mitchell in developing syntaxfiles for formats like yaml and rst.
>>>
>>> Mitchell,
>>>
>>> thank you for Textadept and your generosity,
>>>
>>>
>>> Richard
>>
>> --
>> You are subscribed to code.att.foicica.com <javascript:;>.
>> To change subscription settings, send an e-mail to code+help.att.foicica.com
>> <javascript:;>.
>> To unsubscribe, send an e-mail to code+unsubscribe.att.foicica.com
>> <javascript:;>.
>>
>>
>

-- 
You are subscribed to code.att.foicica.com.
To change subscription settings, send an e-mail to code+help.att.foicica.com.
To unsubscribe, send an e-mail to code+unsubscribe.att.foicica.com.
Received on Tue 05 Jan 2016 - 15:36:31 EST

This archive was generated by hypermail 2.2.0 : Wed 06 Jan 2016 - 06:43:05 EST