modules-interest — Discussion forum for modules usage.

[Modules] Technical Charter adopted

[Xavier D. <xav...@gm...>]

Dear All,

The Technical Charter of the Modules project has been adopted.

This document is available at:
https://modules.readthedocs.io/en/latest/CHARTER.html

Best regards,
Xavier

[Modules] Environment Modules wikipedia page

[Xavier D. <xav...@gm...>]

Hello All,

I am working on improving the Wikipedia page for Environment Modules.
I have just added a History section to provide an overview of the
project’s development from its origins to the present.

I do not know well what happened on the project before 2008. So if
people remember, please check what I have written and tell me if
something is wrong.

https://en.wikipedia.org/wiki/Environment_Modules_(software)#History

Regards,
Xavier

Re: [Modules] module avail is not saying the truth!

[Laurent B. <lau...@ea...>]

Hello Paul,

Thanks for your explanation.

I have used your ".obsolete" trick and it works fine.

Best regards,
Laurent.


-----Message d'origine-----
De : Paul Markfort <pau...@gm...> 
Envoyé : samedi 23 août 2025 16:55
À : mod...@li...
Objet : Re: [Modules] module avail is not saying the truth!

I should add:

"module avail" will list the "a/b" module in both locations, but all commands will operate on the first one.
And, I believe, the same is true of the .modulerc file (only the first one found will be used, and it will apply to both module folders "a/" (even if the only .modulerc is in the second folder - it will apply to both).  Xavier can correct me, if I have that wrong.

Hopefully, this clarifies the situation.

I think if you want to deny access to the first module, you might try making it unreadable (chmod a-r ).  I am not sure if that will work - but it is worth a try (otherwise, just rename or remove it).

As a side note, To get rid of an old module, but save it for posterity - I create an .obsolete folder in the module folder and move it there (you can find it, and put it back if you need to).  This hides it from module avail.


Also, if you want to include pictures - that is fine.
But please also include the complete text output in the message as well.

Thanks.



On 2025-08-22 10:15 AM, Paul Markfort wrote:
> Not a bug.
> This behavior goes way back to the Turn of the Century.
> 
> If you have:
> MODULEPATH=/home/user/modules:/usr/etc/modules/common
> 
> And you have the files:
> /home/user/modules/a/b
> /usr/etc/modules/common/a/b
> 
> 
> Only the first module "a/b" will be visible to the modules command.
> 
> I use this "FEATURE" all the time to test changes to existing modules.
> (copy the module from the second path, to the first - then change an modify the copy and test it).
> 
> 
> 
> 
> On 2025-08-22 5:17 AM, Laurent BESSON wrote:
>> Hello dear Modules users,
>>
>> As an introduction, I have to say I did something weird : I have the same module name in 2 places and both are visible to < module > command.
>>
>> Of course, these 2 modules files have a different content. And I wanted to < forbid > one. So I added in a .modulerc the following line :
>>
>> module-forbid --message "This version has been removed" 
>> /media/TmpStore/users/lbesson/Tools/modulefiles/mentor/questa_lint/20
>> 25.2_1
>>
>> When I run < ml avail mentor/questa_lint>, it says (I include a screenshot to keep colors and nice display) :
>>
>> [cid:image001.png@01DC135D.46C53D90]
>>
>> It shows exactly the expected behaviour. But then I try to load the < available > one and I get this :
>>
>> [cid:image002.png@01DC135E.B4DE18A0]
>>
>> To me, it looks like a bug : I should be allowed to load < 
>> mentor/questa_lint/2025.2_1 > from < /tool/modules >
>>
>> What do you think ?
>>
>> Best regards,
>> Laurent.
>>
>> PS : I'm running Modules 5.5 under RedHat machines
>>
>>
>>
>> _______________________________________________
>> Modules-interest mailing list
>> Mod...@li...
>> https://lists.sourceforge.net/lists/listinfo/modules-interest
>>
> 

--
--------------------------------------------------------
The views and opinions expressed above are strictly those of the author(s).  The content of this message has not been reviewed nor approved by any entity whatsoever.
--------------------------------------------------------
Paul FM         Info: http://paulfm.com/~paulfm/
--------------------------------------------------------


_______________________________________________
Modules-interest mailing list
Mod...@li...
https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] module avail is not saying the truth!

[Paul M. <pau...@gm...>]

I should add:

"module avail" will list the "a/b" module in both locations, but all commands will operate on the first one.
And, I believe, the same is true of the .modulerc file (only the first one found will be used, and it will apply to both module folders "a/" (even if the only .modulerc is in the second folder - it will apply to both).  Xavier can correct me, if I have that wrong.

Hopefully, this clarifies the situation.

I think if you want to deny access to the first module, you might try making it unreadable (chmod a-r ).  I am not sure if that will work - but it is worth a try (otherwise, just rename or remove it).

As a side note, To get rid of an old module, but save it for posterity - I create an .obsolete folder in the module folder and move it there (you can find it, and put it back if you need to).  This hides it from module avail.


Also, if you want to include pictures - that is fine.
But please also include the complete text output in the message as well.

Thanks.



On 2025-08-22 10:15 AM, Paul Markfort wrote:
> Not a bug.
> This behavior goes way back to the Turn of the Century.
> 
> If you have:
> MODULEPATH=/home/user/modules:/usr/etc/modules/common
> 
> And you have the files:
> /home/user/modules/a/b
> /usr/etc/modules/common/a/b
> 
> 
> Only the first module "a/b" will be visible to the modules command.
> 
> I use this "FEATURE" all the time to test changes to existing modules.
> (copy the module from the second path, to the first - then change an modify the copy and test it).
> 
> 
> 
> 
> On 2025-08-22 5:17 AM, Laurent BESSON wrote:
>> Hello dear Modules users,
>>
>> As an introduction, I have to say I did something weird : I have the same module name in 2 places and both are visible to < module > command.
>>
>> Of course, these 2 modules files have a different content. And I wanted to < forbid > one. So I added in a .modulerc the following line :
>>
>> module-forbid --message "This version has been removed" /media/TmpStore/users/lbesson/Tools/modulefiles/mentor/questa_lint/2025.2_1
>>
>> When I run < ml avail mentor/questa_lint>, it says (I include a screenshot to keep colors and nice display) :
>>
>> [cid:image001.png@01DC135D.46C53D90]
>>
>> It shows exactly the expected behaviour. But then I try to load the < available > one and I get this :
>>
>> [cid:image002.png@01DC135E.B4DE18A0]
>>
>> To me, it looks like a bug : I should be allowed to load < mentor/questa_lint/2025.2_1 > from < /tool/modules >
>>
>> What do you think ?
>>
>> Best regards,
>> Laurent.
>>
>> PS : I'm running Modules 5.5 under RedHat machines
>>
>>
>>
>> _______________________________________________
>> Modules-interest mailing list
>> Mod...@li...
>> https://lists.sourceforge.net/lists/listinfo/modules-interest
>>
> 

-- 
--------------------------------------------------------
The views and opinions expressed above are strictly
those of the author(s).  The content of this message has
not been reviewed nor approved by any entity whatsoever.
--------------------------------------------------------
Paul FM         Info: http://paulfm.com/~paulfm/
--------------------------------------------------------

Re: [Modules] module avail is not saying the truth!

[Paul M. <pau...@gm...>]

Not a bug.
This behavior goes way back to the Turn of the Century.

If you have:
MODULEPATH=/home/user/modules:/usr/etc/modules/common

And you have the files:
/home/user/modules/a/b
/usr/etc/modules/common/a/b


Only the first module "a/b" will be visible to the modules command.

I use this "FEATURE" all the time to test changes to existing modules.
(copy the module from the second path, to the first - then change an modify the copy and test it).




On 2025-08-22 5:17 AM, Laurent BESSON wrote:
> Hello dear Modules users,
> 
> As an introduction, I have to say I did something weird : I have the same module name in 2 places and both are visible to < module > command.
> 
> Of course, these 2 modules files have a different content. And I wanted to < forbid > one. So I added in a .modulerc the following line :
> 
> module-forbid --message "This version has been removed" /media/TmpStore/users/lbesson/Tools/modulefiles/mentor/questa_lint/2025.2_1
> 
> When I run < ml avail mentor/questa_lint>, it says (I include a screenshot to keep colors and nice display) :
> 
> [cid:image001.png@01DC135D.46C53D90]
> 
> It shows exactly the expected behaviour. But then I try to load the < available > one and I get this :
> 
> [cid:image002.png@01DC135E.B4DE18A0]
> 
> To me, it looks like a bug : I should be allowed to load < mentor/questa_lint/2025.2_1 > from < /tool/modules >
> 
> What do you think ?
> 
> Best regards,
> Laurent.
> 
> PS : I'm running Modules 5.5 under RedHat machines
> 
> 
> 
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
> 

-- 
--------------------------------------------------------
The views and opinions expressed above are strictly
those of the author(s).  The content of this message has
not been reviewed nor approved by any entity whatsoever.
--------------------------------------------------------
Paul FM         Info: http://paulfm.com/~paulfm/
--------------------------------------------------------

[Modules] module avail is not saying the truth!

[Laurent B. <lau...@ea...>]

Hello dear Modules users,

As an introduction, I have to say I did something weird : I have the same module name in 2 places and both are visible to < module > command.

Of course, these 2 modules files have a different content. And I wanted to < forbid > one. So I added in a .modulerc the following line :

module-forbid --message "This version has been removed" /media/TmpStore/users/lbesson/Tools/modulefiles/mentor/questa_lint/2025.2_1

When I run < ml avail mentor/questa_lint>, it says (I include a screenshot to keep colors and nice display) :

[cid:image001.png@01DC135D.46C53D90]

It shows exactly the expected behaviour. But then I try to load the < available > one and I get this :

[cid:image002.png@01DC135E.B4DE18A0]

To me, it looks like a bug : I should be allowed to load < mentor/questa_lint/2025.2_1 > from < /tool/modules >

What do you think ?

Best regards,
Laurent.

PS : I'm running Modules 5.5 under RedHat machines

[Modules] Modules 5.6.0 released

[Xavier D. <xav...@gm...>]

Hello All,

It is a great pleasure to announce that Modules 5.6 is out! Many new
features have been added, the most prominent are:

* spider sub-command
* Requiring via module
* Always see hidden modules
* Issue warning upon module evaluation
* Simplified way to define module help message
* Support for newline character in environment variable value
* Declare additional elements provided by a module

Details on the major changes included in this new release are provided
in the MIGRATING document. The list of all changes made in this new
version are described in the NEWS document.

 http://modules.readthedocs.io/en/stable/MIGRATING.html
 http://modules.readthedocs.io/en/stable/NEWS.html

The tarball of this new version can be downloaded at:

 http://downloads.sourceforge.net/modules/modules-5.6.0.tar.gz

The zipball to install this new version on Windows platform can be
downloaded at:

 http://downloads.sourceforge.net/modules/modules-5.6.0-win.zip

If you encounter any issue, please let us know by creating a ticket on
the project bug tracker at:

 https://github.com/envmodules/modules/issues

Many thanks to Laurent Besson for his contribution to this release.
Many thanks also to all of you who improve Modules by reporting bugs
or sharing new ideas.

Best regards,
Xavier

[Modules] Requiring *via* modules

[Xavier D. <xav...@gm...>]

Dear All,

The upcoming Modules v5.6 release introduces a new configuration
option: require_via.

This option enables the ability to establish a dependency link between
a via module and the modulefiles located in the modulepath it enables.
With require_via activated, Modules can now fully support the module
hierarchy mechanism.

Full details and examples:
https://modules.readthedocs.io/en/latest/MIGRATING.html#requiring-via-module

Regards,
Xavier

[Modules] spider sub-command

[Xavier D. <xav...@gm...>]

Dear All,

The upcoming Modules 5.6 release will ship a new sub-command: spider.

This sub-command command lists all available modules not only in the
currently enabled modulepaths, but also recursively in any modulepaths
enabled by those modules.

See the following link for details and examples:
https://modules.readthedocs.io/en/latest/MIGRATING.html#spider-sub-command

Regards,
Xavier

[Modules] New provide modulefile command

[Xavier D. <xav...@gm...>]

Dear All,

The upcoming Modules v5.6 release introduces a new "provide"
modulefile command that allows a module to declare additional elements
it offers. These elements are registered as aliases when the module is
loaded, helping fulfill dependencies expressed by other modules.

Full details and examples:
https://modules.readthedocs.io/en/latest/MIGRATING.html#declare-additional-elements-provided-by-a-module

Best regards,
Xavier

[Modules] Always see hidden modules

[Xavier D. <xav...@gm...>]

Dear All,

Next version (5.6) will come with the ability to always see hidden
modules, through the addition of the "hidden" element to the output
configuration options:

https://modules.readthedocs.io/en/latest/MIGRATING.html

Best regards,
Xavier

Re: [Modules] Modulefiles mode for Emacs

[Xavier D. <xav...@gm...>]

Hello All,

Thanks to the contribution of Laurent, a "modulefile-mode" for Emacs
is now available with Modules.

See https://github.com/envmodules/modules/tree/main/share/emacs/lisp

I have adapted RPM spec file to include these Emacs addon files when
installation environment-modules RPM.

Best regards,
Xavier

Le jeu. 12 juin 2025 à 20:29, Xavier Delaruelle
<xav...@gm...> a écrit :
>
> Hello Laurent,
>
> I suggest you create a pull request on GitHub (fork+new
> branch+push+create pull request). Add the new file into directory
> "share/emacs".
>
> Best regards,
> Xavier
>
> Le jeu. 12 juin 2025 à 13:51, Laurent BESSON
> <lau...@ea...> a écrit :
> >
> > Hello Xavier, all
> >
> >
> >
> > I wrote a first version for a Modulefiles mode for Emacs. It relies on existing Tcl mode (tcl-mode) and adds highlighting for the Modulefiles commands.
> >
> >
> >
> > How can we proceed to make it available to anyone ? Do I create a new branch/fork from GitHub or do I send the file (only one, for the time being) directly to you for integration ?
> >
> > If anyone on the list wants to give it a try, I'll be happy to share 😊
> >
> >
> >
> >
> >
> > L.
> >
> >
> >
> > -----Message d'origine-----
> > De : Xavier Delaruelle <xav...@gm...>
> > Envoyé : mercredi 11 juin 2025 18:49
> > À : Environment Modules usage and discussion. <mod...@li...>
> > Objet : Re: [Modules] Modulefiles mode for Emacs
> >
> >
> >
> > Hello Laurent and All,
> >
> >
> >
> > That could be great stuff to contribute to the project. I am not an Emacs user, so I cannot help here. LLM may help but it requires someone with good enough Emacs knowledge to steer it.
> >
> >
> >
> > For Vim, we have already done this job. It is available within https://github.com/envmodules/modules/tree/main/share/vim.
> >
> >
> >
> > Best regards,
> >
> > Xavier
> >
> >
> >
> > Le mer. 11 juin 2025 à 11:58, Laurent BESSON <lau...@ea...> a écrit :
> >
> > >
> >
> > > Hello dear Modules list,
> >
> > >
> >
> > >
> >
> > >
> >
> > > I’m an old fashion guy and I’m still using Emacs as my favorite editor 😊. But I’m pretty sure I’m not the only one in this list.
> >
> > >
> >
> > >
> >
> > >
> >
> > > I was wondering if someone had developped a « mode » to colorize Modulefiles files ? or at least some setup to recognize Modulefiles and use tcl-mode automatically ?
> >
> > >
> >
> > >
> >
> > >
> >
> > > Best regards,
> >
> > >
> >
> > > Laurent.
> >
> > >
> >
> > > _______________________________________________
> >
> > > Modules-interest mailing list
> >
> > > Mod...@li...
> >
> > > https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
> >
> >
> >
> >
> > _______________________________________________
> >
> > Modules-interest mailing list
> >
> > Mod...@li...
> >
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] envml

[Xavier D. <xav...@gm...>]

Thanks for the feedback, I have improved the description a bit.

Best regards,
Xavier

Le ven. 13 juin 2025 à 16:35, Paul Markfort <pau...@gm...> a écrit :
>
> It is a bash script (included with modules).
>
> So it starts a new process - then runs its commands - exiting when done.
>
> Alternatively, you could just write a bash script for the particular situation that loads modules and then runs a command.
>
>
> On 2025-06-13 6:50 AM, InfnPi wrote:
> > I read documentation, but don’t really understand it’s use.
> > What happens after the command is executed?
> > The loaded modules stay or they are just used to run the command and then unloaded?
> >
> > Would be nice to have a “real” usage example with environment before and after the command
> >
> > Roberto
> > On 13 Jun 2025 at 07:56 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
> >> Dear All,
> >>
> >> Do you know the "envml" command?
> >>
> >> Like "env", it runs a program in a modified environment, but here
> >> environment is modified by Modules.
> >>
> >> "envml" is available since Modules 4.0 and it is freshly documented in
> >> its own man page:
> >> https://modules.readthedocs.io/en/latest/envml.html
> >>
> >> Best regards,
> >> Xavier
> >>
> >>
> >> _______________________________________________
> >> Modules-interest mailing list
> >> Mod...@li...
> >> https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
> >
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
>
> --
> --------------------------------------------------------
> The views and opinions expressed above are strictly
> those of the author(s).  The content of this message has
> not been reviewed nor approved by any entity whatsoever.
> --------------------------------------------------------
> Paul FM         Info: http://paulfm.com/~paulfm/
> --------------------------------------------------------
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] envml

[Paul M. <pau...@gm...>]

It is a bash script (included with modules).

So it starts a new process - then runs its commands - exiting when done.

Alternatively, you could just write a bash script for the particular situation that loads modules and then runs a command.


On 2025-06-13 6:50 AM, InfnPi wrote:
> I read documentation, but don’t really understand it’s use.
> What happens after the command is executed?
> The loaded modules stay or they are just used to run the command and then unloaded?
> 
> Would be nice to have a “real” usage example with environment before and after the command
> 
> Roberto
> On 13 Jun 2025 at 07:56 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
>> Dear All,
>>
>> Do you know the "envml" command?
>>
>> Like "env", it runs a program in a modified environment, but here
>> environment is modified by Modules.
>>
>> "envml" is available since Modules 4.0 and it is freshly documented in
>> its own man page:
>> https://modules.readthedocs.io/en/latest/envml.html
>>
>> Best regards,
>> Xavier
>>
>>
>> _______________________________________________
>> Modules-interest mailing list
>> Mod...@li...
>> https://lists.sourceforge.net/lists/listinfo/modules-interest
> 
> 
> 
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
> 

-- 
--------------------------------------------------------
The views and opinions expressed above are strictly
those of the author(s).  The content of this message has
not been reviewed nor approved by any entity whatsoever.
--------------------------------------------------------
Paul FM         Info: http://paulfm.com/~paulfm/
--------------------------------------------------------

Re: [Modules] envml

[InfnPi <rob...@pi...>]

I read documentation, but don’t really understand it’s use.
What happens after the command is executed?
The loaded modules stay or they are just used to run the command and then unloaded?

Would be nice to have a “real” usage example with environment before and after the command

Roberto
On 13 Jun 2025 at 07:56 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
> Dear All,
>
> Do you know the "envml" command?
>
> Like "env", it runs a program in a modified environment, but here
> environment is modified by Modules.
>
> "envml" is available since Modules 4.0 and it is freshly documented in
> its own man page:
> https://modules.readthedocs.io/en/latest/envml.html
>
> Best regards,
> Xavier
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

[Modules] envml

[Xavier D. <xav...@gm...>]

Dear All,

Do you know the "envml" command?

Like "env", it runs a program in a modified environment, but here
environment is modified by Modules.

"envml" is available since Modules 4.0 and it is freshly documented in
its own man page:
  https://modules.readthedocs.io/en/latest/envml.html

Best regards,
Xavier

Re: [Modules] Modulefiles mode for Emacs

[Xavier D. <xav...@gm...>]

Hello Laurent,

I suggest you create a pull request on GitHub (fork+new
branch+push+create pull request). Add the new file into directory
"share/emacs".

Best regards,
Xavier

Le jeu. 12 juin 2025 à 13:51, Laurent BESSON
<lau...@ea...> a écrit :
>
> Hello Xavier, all
>
>
>
> I wrote a first version for a Modulefiles mode for Emacs. It relies on existing Tcl mode (tcl-mode) and adds highlighting for the Modulefiles commands.
>
>
>
> How can we proceed to make it available to anyone ? Do I create a new branch/fork from GitHub or do I send the file (only one, for the time being) directly to you for integration ?
>
> If anyone on the list wants to give it a try, I'll be happy to share 😊
>
>
>
>
>
> L.
>
>
>
> -----Message d'origine-----
> De : Xavier Delaruelle <xav...@gm...>
> Envoyé : mercredi 11 juin 2025 18:49
> À : Environment Modules usage and discussion. <mod...@li...>
> Objet : Re: [Modules] Modulefiles mode for Emacs
>
>
>
> Hello Laurent and All,
>
>
>
> That could be great stuff to contribute to the project. I am not an Emacs user, so I cannot help here. LLM may help but it requires someone with good enough Emacs knowledge to steer it.
>
>
>
> For Vim, we have already done this job. It is available within https://github.com/envmodules/modules/tree/main/share/vim.
>
>
>
> Best regards,
>
> Xavier
>
>
>
> Le mer. 11 juin 2025 à 11:58, Laurent BESSON <lau...@ea...> a écrit :
>
> >
>
> > Hello dear Modules list,
>
> >
>
> >
>
> >
>
> > I’m an old fashion guy and I’m still using Emacs as my favorite editor 😊. But I’m pretty sure I’m not the only one in this list.
>
> >
>
> >
>
> >
>
> > I was wondering if someone had developped a « mode » to colorize Modulefiles files ? or at least some setup to recognize Modulefiles and use tcl-mode automatically ?
>
> >
>
> >
>
> >
>
> > Best regards,
>
> >
>
> > Laurent.
>
> >
>
> > _______________________________________________
>
> > Modules-interest mailing list
>
> > Mod...@li...
>
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
>
>
>
>
>
> _______________________________________________
>
> Modules-interest mailing list
>
> Mod...@li...
>
> https://lists.sourceforge.net/lists/listinfo/modules-interest
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Modulefiles mode for Emacs

[Laurent B. <lau...@ea...>]

Hello Xavier, all



I wrote a first version for a Modulefiles mode for Emacs. It relies on existing Tcl mode (tcl-mode) and adds highlighting for the Modulefiles commands.



How can we proceed to make it available to anyone ? Do I create a new branch/fork from GitHub or do I send the file (only one, for the time being) directly to you for integration ?

If anyone on the list wants to give it a try, I'll be happy to share 😊





L.



-----Message d'origine-----
De : Xavier Delaruelle <xav...@gm...>
Envoyé : mercredi 11 juin 2025 18:49
À : Environment Modules usage and discussion. <mod...@li...>
Objet : Re: [Modules] Modulefiles mode for Emacs



Hello Laurent and All,



That could be great stuff to contribute to the project. I am not an Emacs user, so I cannot help here. LLM may help but it requires someone with good enough Emacs knowledge to steer it.



For Vim, we have already done this job. It is available within https://github.com/envmodules/modules/tree/main/share/vim.



Best regards,

Xavier



Le mer. 11 juin 2025 à 11:58, Laurent BESSON <lau...@ea...<mailto:lau...@ea...>> a écrit :

>

> Hello dear Modules list,

>

>

>

> I’m an old fashion guy and I’m still using Emacs as my favorite editor 😊. But I’m pretty sure I’m not the only one in this list.

>

>

>

> I was wondering if someone had developped a « mode » to colorize Modulefiles files ? or at least some setup to recognize Modulefiles and use tcl-mode automatically ?

>

>

>

> Best regards,

>

> Laurent.

>

> _______________________________________________

> Modules-interest mailing list

> Mod...@li...<mailto:Mod...@li...>

> https://lists.sourceforge.net/lists/listinfo/modules-interest





_______________________________________________

Modules-interest mailing list

Mod...@li...<mailto:Mod...@li...>

https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Modulefiles mode for Emacs

[Xavier D. <xav...@gm...>]

Hello Laurent and All,

That could be great stuff to contribute to the project. I am not an
Emacs user, so I cannot help here. LLM may help but it requires
someone with good enough Emacs knowledge to steer it.

For Vim, we have already done this job. It is available within
https://github.com/envmodules/modules/tree/main/share/vim.

Best regards,
Xavier

Le mer. 11 juin 2025 à 11:58, Laurent BESSON
<lau...@ea...> a écrit :
>
> Hello dear Modules list,
>
>
>
> I’m an old fashion guy and I’m still using Emacs as my favorite editor 😊. But I’m pretty sure I’m not the only one in this list.
>
>
>
> I was wondering if someone had developped a « mode » to colorize Modulefiles files ? or at least some setup to recognize Modulefiles and use tcl-mode automatically ?
>
>
>
> Best regards,
>
> Laurent.
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

[Modules] Modulefiles mode for Emacs

[Laurent B. <lau...@ea...>]

Hello dear Modules list,

I’m an old fashion guy and I’m still using Emacs as my favorite editor 😊. But I’m pretty sure I’m not the only one in this list.

I was wondering if someone had developped a « mode » to colorize Modulefiles files ? or at least some setup to recognize Modulefiles and use tcl-mode automatically ?

Best regards,
Laurent.

[Modules] Support for newline character in environment variable value

[Xavier D. <xav...@gm...>]

Dear All,

Next version (5.6) will add the ability to define environment variable
whose value contains newline character:

https://modules.readthedocs.io/en/latest/MIGRATING.html#support-for-newline-character-in-environment-variable-value

Regards,
Xavier

Re: [Modules] Using variables inside a tcl command

[InfnPi <rob...@pi...>]

Thx

Roberto
On 2 Jun 2025 at 20:27 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
> "colors" configuration option only contains key relative to items that
> are graphically rendered. But you may define these color items easily
> in your initrc configuration file:
>
> module config colors +red=1;31:green=1;32:yellow=1;33:blue=1;34
>
> Regards,
> Xavier
>
> Le lun. 2 juin 2025 à 09:00, InfnPi <rob...@pi...> a écrit :
> >
> > Indeed this seems the best option to me.
> > What would be nice, in order to make it usable site wide and out of the box, would be to define in colors some "standard" nicknames for colors like:
> > red=1;31:green=1;32:yellow=1;33:blue=1;34
> >
> > Roberto
> > On 30 May 2025 at 15:24 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
> >
> > If you use Modules v5.2 or newer version, you may also rely on the
> > "sgr" internal procedure to render text graphically.
> >
> > First, you need to give access to this internal procedure within the
> > modulefile evaluation context. Add the following line in the
> > siteconfig.tcl script (usually installed in /etc/environment-modules):
> >
> > set modulefile_extra_cmds {sgr sgr}
> >
> > Two arguments should be given to sgr proc:
> >
> > sgr color_key text
> >
> > You may rely on the predefined color keys or add your own (through the
> > "colors" configuration option):
> >
> > $ ml config colors
> > Modules Release 5.5.0 (2024-11-11)
> >
> > - Config. name ---------.- Value (set by if default overridden) ---------------
> > colors
> > hi=1:db=2:tr=2:se=2:er=91:wa=93:me=95:in=94:mp=1;94:di=94:al=96:va=93:sy=95:de=4:cm=92:aL=100:L=90;47:H=2:F=41:nF=43:S=46:sS=44:kL=30;48;5;109
> >
> > For example, if you want the text to be rendered like warning message,
> > the modulefile will be:
> >
> > #%Module
> > module-whatis "This is an example using the [sgr wa XX] version"
> >
> > Another advantages to use "sgr" proc is that it does not graphically
> > render text if color mode is disabled by user.
> >
> > Regards,
> > Xavier
> >
> > Le ven. 30 mai 2025 à 14:48, InfnPi <rob...@pi...> a écrit :
> >
> >
> > So I finally managed (with the help of Xavier) to do what i wanted: Write some text to stderr using colors.
> >
> > Here is a simple script that defines and uses a procedure to print out red text using ANSI codes.
> > One thing to be careful about is that being the return value included in quotes (which get evaluated) you need to escape [ inside the return string.
> >
> > ---
> > #%Module
> >
> > proc Red {text} {
> > return "\033\[1;31m$text\033\[0m"
> > }
> >
> > module-whatis "This is an example using the [Red procedure] to color text."
> > ---
> >
> > Roberto
> >
> > Sent with Spark
> > On 29 May 2025 at 19:27 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
> >
> > Hello Roberto,
> >
> > The syntax with double quotes is fine, you have no special character
> > in your text to escape:
> >
> > module-whatis "This module sets up software XXX $ver"
> >
> > You may use an internal variable to use this description at different places:
> >
> > set description "This module sets up software XXX $ver"
> > module-whatis $description
> > proc ModulesHelp {} {
> > puts stderr $::description
> > }
> >
> > For the color, I would use a "color" proc like you did, but I suggest
> > to directly use ANSI SGR code [1] rather calling for tput:
> >
> > return "\033\[1;31m$text\033\[0m"
> >
> > Regards
> > Xavier
> >
> > [1] https://en.wikipedia.org/wiki/ANSI_escape_code#Select_Graphic_Rendition_parameters
> >
> >
> > Le jeu. 29 mai 2025 à 10:32, InfnPi <rob...@pi...> a écrit :
> >
> >
> > Here we go with another question, due to my lack of tcl knowledge.
> >
> > What i would like to achieve is to be able to use variables in text printed to stderr inside a tcl command like module-whatis.
> >
> > Very often in modulefiles you have to refer to the same information in more than one place and therefore it is convenient to use a variable.
> >
> > as an example in a module installing tool XXX version YYY you write something like:
> >
> > module-whatis (This module sets up software XXX version YYY}
> >
> > and
> >
> > proc ModulesHelp {} {
> > puts stderr {This module sets up software XXX version YYY}
> > }
> >
> > Instead of writing "Version YYY" any times in different places it would be nice to be able to use:
> > set ver "Version YYY"
> > and then
> > module-whatis (This module sets up software XXX $ver}
> >
> > this would reduce errors and add maintainability to the modulefile, in the sense that if a new version ZZZ of software XXX comes out i would (probably) use the same modulefile just replacing a few general variables.
> >
> > Unfortunately in using
> > module-watis {This module sets up software XXX $ver} will not expand the variable $ver.
> >
> > A workaround i found is to write it in the following way:
> > module-whatis "This module sets up software XXX $ver"
> > which expands variables (but you have to escape special characters).
> >
> > Is this correct or does it have some unwanted consequences?
> >
> >
> > Along with this question there is a second one i would like to ask:
> >
> > Is there a way to print text to stderr using colors?
> >
> > I found a way to do it defining a procedure and some variables:
> >
> > proc color {color text} {
> > return [exec tput setaf $color]$text[exec tput sgr0]
> > }
> > set red 1
> > set green 2
> > set yellow 3
> > set blue 4
> >
> > and then in the module file i will use:
> > module-whatis "This module sets up software [color $green XXX] $ver"
> >
> > which will print XXX in green.
> >
> > Is there a native way to do the same?
> > Is it fine to use it in the way i described?
> >
> > Again, many thx in advance for all the answers.
> >
> > Roberto
> >
> >
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
> >
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Using variables inside a tcl command

[Xavier D. <xav...@gm...>]

"colors" configuration option only contains key relative to items that
are graphically rendered. But you may define these color items easily
in your initrc configuration file:

module config colors +red=1;31:green=1;32:yellow=1;33:blue=1;34

Regards,
Xavier

Le lun. 2 juin 2025 à 09:00, InfnPi <rob...@pi...> a écrit :
>
> Indeed this seems the best option to me.
> What would be nice, in order to make it usable site wide and out of the box, would be to define in colors some "standard" nicknames for colors like:
> red=1;31:green=1;32:yellow=1;33:blue=1;34
>
> Roberto
> On 30 May 2025 at 15:24 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
>
> If you use Modules v5.2 or newer version, you may also rely on the
> "sgr" internal procedure to render text graphically.
>
> First, you need to give access to this internal procedure within the
> modulefile evaluation context. Add the following line in the
> siteconfig.tcl script (usually installed in /etc/environment-modules):
>
> set modulefile_extra_cmds {sgr sgr}
>
> Two arguments should be given to sgr proc:
>
> sgr color_key text
>
> You may rely on the predefined color keys or add your own (through the
> "colors" configuration option):
>
> $ ml config colors
> Modules Release 5.5.0 (2024-11-11)
>
> - Config. name ---------.- Value (set by if default overridden) ---------------
> colors
> hi=1:db=2:tr=2:se=2:er=91:wa=93:me=95:in=94:mp=1;94:di=94:al=96:va=93:sy=95:de=4:cm=92:aL=100:L=90;47:H=2:F=41:nF=43:S=46:sS=44:kL=30;48;5;109
>
> For example, if you want the text to be rendered like warning message,
> the modulefile will be:
>
> #%Module
> module-whatis "This is an example using the [sgr wa XX] version"
>
> Another advantages to use "sgr" proc is that it does not graphically
> render text if color mode is disabled by user.
>
> Regards,
> Xavier
>
> Le ven. 30 mai 2025 à 14:48, InfnPi <rob...@pi...> a écrit :
>
>
> So I finally managed (with the help of Xavier) to do what i wanted: Write some text to stderr using colors.
>
> Here is a simple script that defines and uses a procedure to print out red text using ANSI codes.
> One thing to be careful about is that being the return value included in quotes (which get evaluated) you need to escape [ inside the return string.
>
> ---
> #%Module
>
> proc Red {text} {
> return "\033\[1;31m$text\033\[0m"
> }
>
> module-whatis "This is an example using the [Red procedure] to color text."
> ---
>
> Roberto
>
> Sent with Spark
> On 29 May 2025 at 19:27 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
>
> Hello Roberto,
>
> The syntax with double quotes is fine, you have no special character
> in your text to escape:
>
> module-whatis "This module sets up software XXX $ver"
>
> You may use an internal variable to use this description at different places:
>
> set description "This module sets up software XXX $ver"
> module-whatis $description
> proc ModulesHelp {} {
> puts stderr $::description
> }
>
> For the color, I would use a "color" proc like you did, but I suggest
> to directly use ANSI SGR code [1] rather calling for tput:
>
> return "\033\[1;31m$text\033\[0m"
>
> Regards
> Xavier
>
> [1] https://en.wikipedia.org/wiki/ANSI_escape_code#Select_Graphic_Rendition_parameters
>
>
> Le jeu. 29 mai 2025 à 10:32, InfnPi <rob...@pi...> a écrit :
>
>
> Here we go with another question, due to my lack of tcl knowledge.
>
> What i would like to achieve is to be able to use variables in text printed to stderr inside a tcl command like module-whatis.
>
> Very often in modulefiles you have to refer to the same information in more than one place and therefore it is convenient to use a variable.
>
> as an example in a module installing tool XXX version YYY you write something like:
>
> module-whatis (This module sets up software XXX version YYY}
>
> and
>
> proc ModulesHelp {} {
> puts stderr {This module sets up software XXX version YYY}
> }
>
> Instead of writing "Version YYY" any times in different places it would be nice to be able to use:
> set ver "Version YYY"
> and then
> module-whatis (This module sets up software XXX $ver}
>
> this would reduce errors and add maintainability to the modulefile, in the sense that if a new version ZZZ of software XXX comes out i would (probably) use the same modulefile just replacing a few general variables.
>
> Unfortunately in using
> module-watis {This module sets up software XXX $ver} will not expand the variable $ver.
>
> A workaround i found is to write it in the following way:
> module-whatis "This module sets up software XXX $ver"
> which expands variables (but you have to escape special characters).
>
> Is this correct or does it have some unwanted consequences?
>
>
> Along with this question there is a second one i would like to ask:
>
> Is there a way to print text to stderr using colors?
>
> I found a way to do it defining a procedure and some variables:
>
> proc color {color text} {
> return [exec tput setaf $color]$text[exec tput sgr0]
> }
> set red 1
> set green 2
> set yellow 3
> set blue 4
>
> and then in the module file i will use:
> module-whatis "This module sets up software [color $green XXX] $ver"
>
> which will print XXX in green.
>
> Is there a native way to do the same?
> Is it fine to use it in the way i described?
>
> Again, many thx in advance for all the answers.
>
> Roberto
>
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
>
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Using variables inside a tcl command

[InfnPi <rob...@pi...>]

Indeed this seems the best option to me.
What would be nice, in order to make it usable site wide and out of the box, would be to define in colors some "standard" nicknames for colors like:
red=1;31:green=1;32:yellow=1;33:blue=1;34

Roberto
On 30 May 2025 at 15:24 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
> If you use Modules v5.2 or newer version, you may also rely on the
> "sgr" internal procedure to render text graphically.
>
> First, you need to give access to this internal procedure within the
> modulefile evaluation context. Add the following line in the
> siteconfig.tcl script (usually installed in /etc/environment-modules):
>
> set modulefile_extra_cmds {sgr sgr}
>
> Two arguments should be given to sgr proc:
>
> sgr color_key text
>
> You may rely on the predefined color keys or add your own (through the
> "colors" configuration option):
>
> $ ml config colors
> Modules Release 5.5.0 (2024-11-11)
>
> - Config. name ---------.- Value (set by if default overridden) ---------------
> colors
> hi=1:db=2:tr=2:se=2:er=91:wa=93:me=95:in=94:mp=1;94:di=94:al=96:va=93:sy=95:de=4:cm=92:aL=100:L=90;47:H=2:F=41:nF=43:S=46:sS=44:kL=30;48;5;109
>
> For example, if you want the text to be rendered like warning message,
> the modulefile will be:
>
> #%Module
> module-whatis "This is an example using the [sgr wa XX] version"
>
> Another advantages to use "sgr" proc is that it does not graphically
> render text if color mode is disabled by user.
>
> Regards,
> Xavier
>
> Le ven. 30 mai 2025 à 14:48, InfnPi <rob...@pi...> a écrit :
> >
> > So I finally managed (with the help of Xavier) to do what i wanted: Write some text to stderr using colors.
> >
> > Here is a simple script that defines and uses a procedure to print out red text using ANSI codes.
> > One thing to be careful about is that being the return value included in quotes (which get evaluated) you need to escape [ inside the return string.
> >
> > ---
> > #%Module
> >
> > proc Red {text} {
> > return "\033\[1;31m$text\033\[0m"
> > }
> >
> > module-whatis "This is an example using the [Red procedure] to color text."
> > ---
> >
> > Roberto
> >
> > Sent with Spark
> > On 29 May 2025 at 19:27 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
> >
> > Hello Roberto,
> >
> > The syntax with double quotes is fine, you have no special character
> > in your text to escape:
> >
> > module-whatis "This module sets up software XXX $ver"
> >
> > You may use an internal variable to use this description at different places:
> >
> > set description "This module sets up software XXX $ver"
> > module-whatis $description
> > proc ModulesHelp {} {
> > puts stderr $::description
> > }
> >
> > For the color, I would use a "color" proc like you did, but I suggest
> > to directly use ANSI SGR code [1] rather calling for tput:
> >
> > return "\033\[1;31m$text\033\[0m"
> >
> > Regards
> > Xavier
> >
> > [1] https://en.wikipedia.org/wiki/ANSI_escape_code#Select_Graphic_Rendition_parameters
> >
> >
> > Le jeu. 29 mai 2025 à 10:32, InfnPi <rob...@pi...> a écrit :
> >
> >
> > Here we go with another question, due to my lack of tcl knowledge.
> >
> > What i would like to achieve is to be able to use variables in text printed to stderr inside a tcl command like module-whatis.
> >
> > Very often in modulefiles you have to refer to the same information in more than one place and therefore it is convenient to use a variable.
> >
> > as an example in a module installing tool XXX version YYY you write something like:
> >
> > module-whatis (This module sets up software XXX version YYY}
> >
> > and
> >
> > proc ModulesHelp {} {
> > puts stderr {This module sets up software XXX version YYY}
> > }
> >
> > Instead of writing "Version YYY" any times in different places it would be nice to be able to use:
> > set ver "Version YYY"
> > and then
> > module-whatis (This module sets up software XXX $ver}
> >
> > this would reduce errors and add maintainability to the modulefile, in the sense that if a new version ZZZ of software XXX comes out i would (probably) use the same modulefile just replacing a few general variables.
> >
> > Unfortunately in using
> > module-watis {This module sets up software XXX $ver} will not expand the variable $ver.
> >
> > A workaround i found is to write it in the following way:
> > module-whatis "This module sets up software XXX $ver"
> > which expands variables (but you have to escape special characters).
> >
> > Is this correct or does it have some unwanted consequences?
> >
> >
> > Along with this question there is a second one i would like to ask:
> >
> > Is there a way to print text to stderr using colors?
> >
> > I found a way to do it defining a procedure and some variables:
> >
> > proc color {color text} {
> > return [exec tput setaf $color]$text[exec tput sgr0]
> > }
> > set red 1
> > set green 2
> > set yellow 3
> > set blue 4
> >
> > and then in the module file i will use:
> > module-whatis "This module sets up software [color $green XXX] $ver"
> >
> > which will print XXX in green.
> >
> > Is there a native way to do the same?
> > Is it fine to use it in the way i described?
> >
> > Again, many thx in advance for all the answers.
> >
> > Roberto
> >
> >
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
> >
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Using variables inside a tcl command

[Xavier D. <xav...@gm...>]

If you use Modules v5.2 or newer version, you may also rely on the
"sgr" internal procedure to render text graphically.

First, you need to give access to this internal procedure within the
modulefile evaluation context. Add the following line in the
siteconfig.tcl script (usually installed in /etc/environment-modules):

set modulefile_extra_cmds {sgr sgr}

Two arguments should be given to sgr proc:

sgr color_key text

You may rely on the predefined color keys or add your own (through the
"colors" configuration option):

$ ml config colors
Modules Release 5.5.0 (2024-11-11)

- Config. name ---------.- Value (set by if default overridden) ---------------
colors
hi=1:db=2:tr=2:se=2:er=91:wa=93:me=95:in=94:mp=1;94:di=94:al=96:va=93:sy=95:de=4:cm=92:aL=100:L=90;47:H=2:F=41:nF=43:S=46:sS=44:kL=30;48;5;109

For example, if you want the text to be rendered like warning message,
the modulefile will be:

#%Module
module-whatis "This is an example using the [sgr wa XX] version"

Another advantages to use "sgr" proc is that it does not graphically
render text if color mode is disabled by user.

Regards,
Xavier

Le ven. 30 mai 2025 à 14:48, InfnPi <rob...@pi...> a écrit :
>
> So I finally managed (with the help of Xavier) to do what i wanted: Write some text to stderr using colors.
>
> Here is a simple script that defines and uses a procedure to print out red text using ANSI codes.
> One thing to be careful about is that being the return value included in quotes (which get evaluated) you need to escape [ inside the return string.
>
> ---
> #%Module
>
> proc Red {text} {
>    return "\033\[1;31m$text\033\[0m"
> }
>
> module-whatis "This is an example using the [Red procedure] to color text."
> ---
>
> Roberto
>
> Sent with Spark
> On 29 May 2025 at 19:27 +0200, Xavier Delaruelle <xav...@gm...>, wrote:
>
> Hello Roberto,
>
> The syntax with double quotes is fine, you have no special character
> in your text to escape:
>
> module-whatis "This module sets up software XXX $ver"
>
> You may use an internal variable to use this description at different places:
>
> set description "This module sets up software XXX $ver"
> module-whatis $description
> proc ModulesHelp {} {
> puts stderr $::description
> }
>
> For the color, I would use a "color" proc like you did, but I suggest
> to directly use ANSI SGR code [1] rather calling for tput:
>
> return "\033\[1;31m$text\033\[0m"
>
> Regards
> Xavier
>
> [1] https://en.wikipedia.org/wiki/ANSI_escape_code#Select_Graphic_Rendition_parameters
>
>
> Le jeu. 29 mai 2025 à 10:32, InfnPi <rob...@pi...> a écrit :
>
>
> Here we go with another question, due to my lack of tcl knowledge.
>
> What i would like to achieve is to be able to use variables in text printed to stderr inside a tcl command like module-whatis.
>
> Very often in modulefiles you have to refer to the same information in more than one place and therefore it is convenient to use a variable.
>
> as an example in a module installing tool XXX version YYY you write something like:
>
> module-whatis (This module sets up software XXX version YYY}
>
> and
>
> proc ModulesHelp {} {
> puts stderr {This module sets up software XXX version YYY}
> }
>
> Instead of writing "Version YYY" any times in different places it would be nice to be able to use:
> set ver "Version YYY"
> and then
> module-whatis (This module sets up software XXX $ver}
>
> this would reduce errors and add maintainability to the modulefile, in the sense that if a new version ZZZ of software XXX comes out i would (probably) use the same modulefile just replacing a few general variables.
>
> Unfortunately in using
> module-watis {This module sets up software XXX $ver} will not expand the variable $ver.
>
> A workaround i found is to write it in the following way:
> module-whatis "This module sets up software XXX $ver"
> which expands variables (but you have to escape special characters).
>
> Is this correct or does it have some unwanted consequences?
>
>
> Along with this question there is a second one i would like to ask:
>
> Is there a way to print text to stderr using colors?
>
> I found a way to do it defining a procedure and some variables:
>
> proc color {color text} {
> return [exec tput setaf $color]$text[exec tput sgr0]
> }
> set red 1
> set green 2
> set yellow 3
> set blue 4
>
> and then in the module file i will use:
> module-whatis "This module sets up software [color $green XXX] $ver"
>
> which will print XXX in green.
>
> Is there a native way to do the same?
> Is it fine to use it in the way i described?
>
> Again, many thx in advance for all the answers.
>
> Roberto
>
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest