mailing-list for TeXmacs Users

[TeXmacs <address@hidden>]

Just a few thoughts.

First of all, it is nice if the TeXmacs version can directly
be browsed at github.  This is possible by directly loading the URL

    https://raw.githubusercontent.com/texmacs/notes/main/src/index.tm

in the editor using C-x C-f (Emacs profile).  One problem is that
the 'notes' style is not part of TeXmacs, so we might have to add
this style directly to TeXmacs.

Secondly, I recommend to use a similar structure for your sources
as for the TeXmacs website (see in particular the tmweb2 style).
In particular, every page comes with a standard title and footer,
which makes it easier to browse the website and adjust the style
to be used on the web using CSS.

Best wishes, --Joris


On Sun, Nov 08, 2020 at 06:05:42PM +0100, TeXmacs wrote:
> Thanks Max for setting up this Wiki.
> I think that this is a good intermediate solution.
> 
> Indeed, it is best for the Wiki to be written in TeXmacs and
> to use the conversion tools to build a web export.
> When we will have an actual TeXmacs server,
> it should be easy to migrate a TeXmacs-based wiki to
> the server so as to make it even more interactive.
> 
> Please experiment with the Wiki for a few weeks.
> When the structure will have stabilized,
> I will add a link on our website.
> 
> Best wishes, --Joris
> 
> 
> On Sun, Nov 08, 2020 at 05:47:30PM +0100, Massimiliano Gubinelli wrote:
> >    Giovanni,
> >     I think we need some experimentation to understand which setup fits 
> > well
> >    with TeXmacs. 
> >    Some time ago Darcy also setup a blog here:
> >    [1]https://texmacs.github.io/blog/
> >    which however has somewhat more complex internal structure which uses 
> > the
> >    software Hugo, and as far as I understand, convert the TeXmacs 
> > documents
> >    first into Markdown to be used by Hugo to build the static site. 
> >    In my opinion it would be better to avoid using external programs. 
> > TeXmacs
> >    can do everything we need and without conversion to Markdown which 
> > looses
> >    information in the process. Of course the final goal is to have
> >    informations published, so I do not care too much on the how. I'm open 
> > to
> >    discuss.
> >    Best
> >    Max
> > 
> >      On 8. Nov 2020, at 16:26, Giovanni Piredda <[2]address@hidden>
> >      wrote:
> >      Hi Massimiliano,
> > 
> >      this is very nice.
> > 
> >      I think in the next few days I will try and post a small article. 
> > Maybe
> >      my first contribution will be a guide on how to make a contribution
> >      (unless someone else writes it before me ;-) ), since I think that 
> > it is
> >      important to make contributions easy :-)
> > 
> >      By the way perhaps it is the case to integrate this repository with 
> > the
> >      TeXmacs developer wiki ([3]https://github.com/texmacs/texmacs/wiki).
> >      Maybe by migrating the articles? But here maybe Darcy can say 
> > something.
> > 
> >      I will also write a few more lines of response here on the mailing 
> > list
> >      to both you and Joris, as I would like to get my point ("TeXmacs will
> >      benefit from making it easy for people to contribute") across.
> > 
> >      Giovanni
> > 
> >      On 08.11.20 16:07, Massimiliano Gubinelli wrote:
> > 
> >        Dear Giovanni, dear all,
> >         I've hacked up a beginning of a Blog/Wiki for TexMacs along the 
> > lines
> >        below (statically generated site/git managed/github hosted).
> > 
> >        You find the repository here:
> > 
> >        [4]https://github.com/texmacs/notes
> >        <[5]https://github.com/texmacs/notes>
> > 
> >        and the static web site served here:
> > 
> >        [6]https://texmacs.github.io/notes/
> >        <[7]https://texmacs.github.io/notes/>
> > 
> >        The TeXmacs sources for the site are in the src/ directory in the
> >        repository. The website can be generated (via
> >        "Tools->Web->Create/Update web site") within TeXmacs. Once the
> >        repository is pushed on github it becomes visible. Please feel 
> > free to
> >        improve/add content/make pull requests.
> > 
> >        We can experiment to see how it goes and if it works for us. In my
> >        opinion is a relatively simple solution which has the advantage 
> > that
> >        one can clone and browse from within TeXmacs.
> > 
> >        Best
> >        Max
> > 
> >          On 8. Nov 2020, at 09:55, Massimiliano Gubinelli 
> > <[8]address@hidden
> >          <[9]mailto:address@hidden>> wrote:
> > 
> >          Dear Giovanni,
> > 
> >          I'm not expert in this matter, but I would tend to suggest that 
> > we
> >          use git-oriented approach, i.e. we collect/build the
> >          wiki/blog/manual as a git repository and maybe publish it via
> >          services like github.
> > 
> >          In my mind this has some advantage for us: we are not bound to 
> > some
> >          CMS, and we can manage the material the way we want, e.g. by 
> > writing
> >          the posts in TeXmacs,  exporting them as html and committing to 
> > the
> >          repository.
> > 
> >          I think people which want to contribute can just provide PR.
> > 
> >          This will allow us to work within TeXmacs. Also the material can 
> > be
> >          made accessible as tm files which can then be viewed directly in
> >          TeXmacs and not in the browser, improving the rendering and
> >          (hopefully) the experience.
> > 
> >          With time one can imagine to code some macro to automatically 
> > edit
> >          and request pulls within TeXmacs, bypassing completely the 
> > browser.
> >          :)
> > 
> >          Best,
> >          Max
> > 
> >            On 4. Nov 2020, at 18:21, Giovanni Piredda <[10]address@hidden
> >            <[11]mailto:address@hidden>> wrote:
> > 
> >            Dear all,
> > 
> >            I think a wiki for TeXmacs, written in good part by users, 
> > could
> >            be helpful.
> > 
> >            There used to be one - still linked from
> >            [12]http://www.texmacs.org/tmweb/help/informal.en.html
> >            <[13]http://www.texmacs.org/tmweb/help/informal.en.html> and 
> > saved
> >            on the "Internet Archive"
> >            
> > ([14]http://web.archive.org/web/20051107175054/alqua.com/tmresources/FrontPage
> >            
> > <[15]http://web.archive.org/web/20051107175054/alqua.com/tmresources/FrontPage>);
> >            at the moment there is a wiki on GitHub, at
> >            [16]https://github.com/texmacs/texmacs/wiki
> >            <[17]https://github.com/texmacs/texmacs/wiki>. I did not
> >            understand how to edit the GitHub wiki (as suggested here:
> >            [18]http://forum.texmacs.cn/t/a-wiki-for-texmacs/71/2
> >            <[19]http://forum.texmacs.cn/t/a-wiki-for-texmacs/71/2>) but it
> >            might be through pull requests.
> > 
> >            A user-maintained TeXmacs wiki could be helpful for TeXmacs and
> >            therefore for all people that use it. Wiki topics relatively 
> > easy
> >            to write up are syntheses of good mailing-list answers - I am
> >            available to write some of them and this could become a FAQ.
> > 
> >            Another good use of the wiki would be in my opinion a 
> > collection
> >            of links to plugins written by people not on the development 
> > team.
> >            I got the idea from the DokuWiki website, here:
> >            [20]https://www.dokuwiki.org/plugins
> >            <[21]https://www.dokuwiki.org/plugins> and especially here:
> >            
> > [22]https://www.dokuwiki.org/devel:plugins#publishing_a_plugin_on_dokuwikiorg
> >            
> > <[23]https://www.dokuwiki.org/devel:plugins#publishing_a_plugin_on_dokuwikiorg>;
> >            the software itself would be in other repositories, the wiki 
> > would
> >            contain links, descriptions and instructions. This would on one
> >            hand set the necessary distance between the software written by
> >            the development team and the user contributions (clear 
> > separation)
> >            and on the other hand would both show prospective users what is
> >            available and hopefully encourage current and prospective 
> > users to
> >            contribute more. Since uploads would not be permitted, this is
> >            probably quite safe and takes less work (maybe just very 
> > little)
> >            to manage.
> > 
> >            For the wiki itself, if the GitHub one is the one that the
> >            developers would like to have, I would suggest to
> > 
> >            - write up instructions on how to contribute
> > 
> >            - put a link to it from the [24]texmacs.org
> >            <[25]http://texmacs.org> website
> > 
> >            Another possibility is DokuWiki. On
> >            [26]https://www.dokuwiki.org/faq:license#dokuwiki_software
> >            <[27]https://www.dokuwiki.org/faq:license#dokuwiki_software> it
> >            says that it is released under the GPL so it is appropriate 
> > for a
> >            wiki on a free software project. I use it privately and it has
> >            been easy and quick to set up for my private use, maybe it 
> > will be
> >            easy to set it up for public use too (I do not know). Again 
> > IMO,
> >            it should be linked to from the [28]texmacs.org
> >            <[29]http://texmacs.org> website (it could be even part of
> >            [30]texmacs.org <[31]http://texmacs.org>, but maybe the 
> > designs do
> >            not fit together well).
> > 
> >            A debate on the wiki topic would be nice :-)
> > 
> >            Giovanni
> > 
> > References
> > 
> >    Visible links
> >    1. https://texmacs.github.io/blog/
> >    2. mailto:address@hidden
> >    3. https://github.com/texmacs/texmacs/wiki
> >    4. https://github.com/texmacs/notes
> >    5. https://github.com/texmacs/notes
> >    6. https://texmacs.github.io/notes/
> >    7. https://texmacs.github.io/notes/
> >    8. mailto:address@hidden
> >    9. mailto:address@hidden
> >   10. mailto:address@hidden
> >   11. mailto:address@hidden
> >   12. http://www.texmacs.org/tmweb/help/informal.en.html
> >   13. http://www.texmacs.org/tmweb/help/informal.en.html
> >   14. 
> > http://web.archive.org/web/20051107175054/alqua.com/tmresources/FrontPage
> >   15. 
> > http://web.archive.org/web/20051107175054/alqua.com/tmresources/FrontPage
> >   16. https://github.com/texmacs/texmacs/wiki
> >   17. https://github.com/texmacs/texmacs/wiki
> >   18. http://forum.texmacs.cn/t/a-wiki-for-texmacs/71/2
> >   19. http://forum.texmacs.cn/t/a-wiki-for-texmacs/71/2
> >   20. https://www.dokuwiki.org/plugins
> >   21. https://www.dokuwiki.org/plugins
> >   22. 
> > https://www.dokuwiki.org/devel:plugins#publishing_a_plugin_on_dokuwikiorg
> >   23. 
> > https://www.dokuwiki.org/devel:plugins#publishing_a_plugin_on_dokuwikiorg
> >   24. http://texmacs.org/
> >   25. http://texmacs.org/
> >   26. https://www.dokuwiki.org/faq:license#dokuwiki_software
> >   27. https://www.dokuwiki.org/faq:license#dokuwiki_software
> >   28. http://texmacs.org/
> >   29. http://texmacs.org/
> >   30. http://texmacs.org/
> >   31. http://texmacs.org/
> > /usr/bin/xdg-open: line 402: htmlview: command not found
> > /usr/bin/xdg-open: line 402: firefox: command not found
> > /usr/bin/xdg-open: line 402: mozilla: command not found
> > /usr/bin/xdg-open: line 402: netscape: command not found