Re: Problem with csh
Deleted ~/.csh. Problem solved. On 07/02/2022 05:23 PM, Will Mengarini wrote: On Sat, Jul 02, 2022 at 01:18:08PM -0400, Stephen P. Molnar wrote: comp@AbNormal:~$ csh Bad : modifier in $ '/'. On Sat, Jul 02, 2022 at 03:31:12PM -0400, Bijan Soleymani wrote: Quick Google search shows it is an issue with the syntax of defining environment variables: https://stackoverflow.com/questions/40968061/bad-modifier-in * Greg Wooledge [22-07/02=Sa 15:41 -0400]: That still requires some command to have been executed. Since Stephen didn't even run a command yet, that means he has to have created a bogus dot file (e.g. ~/.cshrc) containing the invalid csh command. There could be an error in a system-wide init file. He says this is a fresh Bullseye, but not that he's the sysadmin who set it up, and he's in an academic environment. On a Manjaro system that I don't administer I saw the line set -r autologout 86400 which should be set -r autologout = 86400 and after the sysadmin fixed it, a Manjaro update broke it again. Because csh gets little use nowadays, it's possible there's something wrong in Debian's init files too (not the set -r error though, because that gives a different error message), though I assume that whatever is wrong would need to be on a code path not followed for most testing. That seems plausible, since the behavior of startup files could depend on hardware configuration. -- Stephen P. Molnar, Ph.D. Molecular Modeling 614.312.7528 (c) Skype: smolnar1
Re: Problem with csh
On Sat, Jul 02, 2022 at 01:18:08PM -0400, Stephen P. Molnar wrote: comp@AbNormal:~$ csh Bad : modifier in $ '/'. On Sat, Jul 02, 2022 at 03:31:12PM -0400, Bijan Soleymani wrote: >> Quick Google search shows it is an issue with the syntax of defining >> environment variables: >> https://stackoverflow.com/questions/40968061/bad-modifier-in * Greg Wooledge [22-07/02=Sa 15:41 -0400]: > That still requires some command to have been executed. Since Stephen > didn't even run a command yet, that means he has to have created a > bogus dot file (e.g. ~/.cshrc) containing the invalid csh command. There could be an error in a system-wide init file. He says this is a fresh Bullseye, but not that he's the sysadmin who set it up, and he's in an academic environment. On a Manjaro system that I don't administer I saw the line set -r autologout 86400 which should be set -r autologout = 86400 and after the sysadmin fixed it, a Manjaro update broke it again. Because csh gets little use nowadays, it's possible there's something wrong in Debian's init files too (not the set -r error though, because that gives a different error message), though I assume that whatever is wrong would need to be on a code path not followed for most testing. That seems plausible, since the behavior of startup files could depend on hardware configuration.
Re: Problem with csh
Stephen P. Molnar wrote: > comp@AbNormal:~$ csh > Bad : modifier in $ '/'. A colon ":" is a modifier in the tcsh for variables. For instance: set f=file.c echo $f:r --> output: file [note the missing ".c", only root name] echo $f:e --> output: c [note that "file." is missing, only the extension] So, I assume, you used somewhere a ":/" in the script and "/" is no valid modifier. Maybe you should run the script under a csh [comparable with sh], and not a tcsh [comparable with bash]? csh has no modifiers, but tcsh has. Regards, Klaus. -- Klaus Singvogel GnuPG-Key-ID: 1024R/5068792D 1994-06-27
Re: Problem with csh
On Sat, Jul 02, 2022 at 03:31:12PM -0400, Bijan Soleymani wrote: > On 2022-07-02 14:24, Greg Wooledge wrote: > > On Sat, Jul 02, 2022 at 01:18:08PM -0400, Stephen P. Molnar wrote: > > > I have one application that I compile which requires the csh shell. > > > > > > > comp@AbNormal:~$ csh > > > Bad : modifier in $ '/'. > > > AbNormal:~% > > > > > > I've never seen this before but the compilation process still worked. > > > > > > What's going on? > > > > Ask your academia comrades. Nobody outside of academia will know, > > because > > nobody else still uses csh. For anything. It's just bad. > > Quick Google search shows it is an issue with the syntax of defining > environment variables: > https://stackoverflow.com/questions/40968061/bad-modifier-in That still requires some command to have been executed. Since Stephen didn't even run a command yet, that means he has to have created a bogus dot file (e.g. ~/.cshrc) containing the invalid csh command. One may wonder why the fact that "oh by the way I created a .cshrc file first, *then* ran csh, and here's what's in that file" was not shown, but I've learned not to expect any approximation of common sense.
Re: Problem with csh
On 2022-07-02 14:24, Greg Wooledge wrote: On Sat, Jul 02, 2022 at 01:18:08PM -0400, Stephen P. Molnar wrote: I have one application that I compile which requires the csh shell. comp@AbNormal:~$ csh Bad : modifier in $ '/'. AbNormal:~% I've never seen this before but the compilation process still worked. What's going on? Ask your academia comrades. Nobody outside of academia will know, because nobody else still uses csh. For anything. It's just bad. Quick Google search shows it is an issue with the syntax of defining environment variables: https://stackoverflow.com/questions/40968061/bad-modifier-in Bijan
Re: Problem with csh
On Sat, Jul 02, 2022 at 01:18:08PM -0400, Stephen P. Molnar wrote: > I have one application that I compile which requires the csh shell. What does that even *mean*? If one of the *scripts* that you *execute* during the build uses csh, well, OK. I would write off that particular application as "likely to be broken", but IIRC you do a lot of "academia" stuff, and academia clung to csh long after it had already begun to smell funny. But having a *script* that needs csh does not mean you need to run csh as your *interactive* shell. That's totally different. > comp@AbNormal:~$ csh > Bad : modifier in $ '/'. > AbNormal:~% > > I've never seen this before but the compilation process still worked. > > What's going on? Ask your academia comrades. Nobody outside of academia will know, because nobody else still uses csh. For anything. It's just bad.
Problem with csh
I am running a new installation of Bullseye with the bash shell. I have one application that I compile which requires the csh shell. WHen I change from bash to csh I get: comp@AbNormal:~$ csh Bad : modifier in $ '/'. AbNormal:~% I've never seen this before but the compilation process still worked. What's going on? Thanks in advance -- Stephen P. Molnar, Ph.D. Molecular Modeling 614.312.7528 (c) Skype: smolnar1
