* alias appears to not work inside a called bash script
@ 2017-08-21 22:30 Michel LaBarre
2017-08-21 22:53 ` Eliot Moss
` (2 more replies)
0 siblings, 3 replies; 24+ messages in thread
From: Michel LaBarre @ 2017-08-21 22:30 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
Hello all,
I have a 4 line bash script:
#!/bin/bash
alias nawk=gawk
alias nawk
nawk 'BEGIN {FS="^"} ; (length($0) > maxline) { maxline = length($0) ;
line=$0} ; END{print maxline, line}' $*
When I run the script I see:
alias nawk='gawk'
/cygdrive/c/mybin/maxline/: line 4: nawk: command not found
It looks like the alias is properly defined but it does not appear to take
effect.
Same thing happens if I alias to awk instead of qawk.
Same thing happens if I define the alias in .bashrc (I include an echo in
bashrc to confirm that it is being invoked).
My .bashrc is not likely a factor - I empty it and the result is the same.
No carriage returns in the script or .bashrc.
I have updated everything August 5th using setup and letting all "Pending"
pkgs update so I believe I am up to date.
The funny thing is that it works ok from an interactive session, whether the
alias is explicitly defined in the session or in .bashrc.
Thank you in advance for any insights.
BTW - I just re-subscribed to cygwin 4-5 hours ago and have not seen any
mail which seems unusual based on past experience.
Michel LaBarre
613-692-0507
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 37230 bytes --]
Cygwin Configuration Diagnostics
Current System Time: Mon Aug 21 18:22:17 2017
Windows 10 Home Ver 10.0 Build 15063
Path: C:\cygwin64\bin
.
C:\Program Files (x86)\Intel\iCLS Client
C:\Program Files\Intel\iCLS Client
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT
C:\mybinlocal
C:\mybin
C:\cygwin64\bin
C:\Program Files\Intel\WiFi\bin
C:\Program Files\Common Files\Intel\WirelessCommon
C:\Users\michel\AppData\Local\Microsoft\WindowsApps
Output from C:\cygwin64\bin\id.exe
UID: 197609(michel) GID: 197121(None)
197121(None) 545(Users)
4(INTERACTIVE) 66049(CONSOLE LOGON)
11(Authenticated Users) 15(This Organization)
113(Local account) 66048(LOCAL)
262154(NTLM Authentication) 4294967295(Unknown+Group)
401408(Medium Mandatory Level)
SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS
PWD = '/cygdrive/c/mybin'
HOME = '/cygdrive/d/michel'
CYGWIN = 'glob:ignorecase'
USERDOMAIN = 'SPIRO1'
OS = 'Windows_NT'
COMMONPROGRAMFILES = 'C:\Program Files\Common Files'
PROCESSOR_LEVEL = '6'
PSModulePath = 'C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules'
CommonProgramW6432 = 'C:\Program Files\Common Files'
!ExitCode = '0000007F'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
PUBLIC = 'C:\Users\Public'
USERNAME = 'michel'
LOGONSERVER = '\\SPIRO1'
PROCESSOR_ARCHITECTURE = 'AMD64'
LOCALAPPDATA = 'C:\Users\michel\AppData\Local'
!D: = 'd:\michel'
COMPUTERNAME = 'SPIRO1'
TTYIn = '/dev/cons0'
SYSTEMDRIVE = 'C:'
USERPROFILE = 'C:\Users\michel'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.SH'
SYSTEMROOT = 'C:\WINDOWS'
USERDOMAIN_ROAMINGPROFILE = 'SPIRO1'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 78 Stepping 3, GenuineIntel'
DEVNULL = '/dev/null'
TMP = '/cygdrive/c/Users/michel/AppData/Local/Temp'
HOST = 'spiro1'
BASH_ENV = 'd:/michel/.bashrc'
OneDrive = 'C:\Users\michel\OneDrive'
TTYOut = '/dev/cons0'
PROCESSOR_REVISION = '4e03'
TMPDIR = '/cygdrive/c/Users/michel/AppData/Local/Temp'
PROMPT = '$P$G'
NUMBER_OF_PROCESSORS = '4'
ProgramW6432 = 'C:\Program Files'
COMSPEC = 'C:\WINDOWS\system32\cmd.exe'
APPDATA = 'C:\Users\michel\AppData\Roaming'
TERM = 'cygwin'
WINDIR = 'C:\WINDOWS'
ProgramData = 'C:\ProgramData'
SHLVL = '1'
PROGRAMFILES = 'C:\Program Files'
ALLUSERSPROFILE = 'C:\ProgramData'
TEMP = '/cygdrive/c/Users/michel/AppData/Local/Temp'
SESSIONNAME = 'Console'
ProgramFiles(x86) = 'C:\Program Files (x86)'
HOMEDRIVE = 'C:'
HOMEPATH = '\Users\michel'
mybin = 'c:\mybin'
EXECIGNORE = '*.dll'
BASH_FUNC_lsd%% = '() { ls -log $* | grep "^d"
}'
_ = '/usr/bin/cygcheck'
OLDPWD = '/cygdrive/d/michel'
HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
(default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
(default) = '\??\c:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
(default) = 'C:\cygwin64'
obcaseinsensitive set to 1
Cygwin installations found in the registry:
System: Key: e022582115c10879 Path: c:\cygwin64
User: Key: e022582115c10879 Path: C:\cygwin64
c: hd NTFS 133259Mb 38% CP CS UN PA FC EN
d: hd NTFS 807294Mb 39% CP CS UN PA FC EN
r: cd N/A N/A
y: net NTFS 107526Mb 78% CP CS UN PA FC EN
z: net NTFS 354364Mb 80% CP CS UN PA FC EN
C:\cygwin64 / system binary,auto
C:\cygwin64\bin /usr/bin system binary,auto
C:\cygwin64\lib /usr/lib system binary,auto
cygdrive prefix /cygdrive user binary,noacl,posix=0,auto
Found: C:\cygwin64\bin\awk
Found: C:\cygwin64\bin\awk
-> C:\cygwin64\bin\gawk.exe
Found: C:\cygwin64\bin\bash.exe
Found: C:\cygwin64\bin\bash.exe
Found: C:\cygwin64\bin\cat.exe
Found: C:\cygwin64\bin\cat.exe
Found: C:\cygwin64\bin\cp.exe
Found: C:\cygwin64\bin\cp.exe
Not Found: cpp (good!)
Not Found: crontab
Found: C:\cygwin64\bin\find.exe
Found: C:\WINDOWS\system32\find.exe
Warning: C:\cygwin64\bin\find.exe hides C:\WINDOWS\system32\find.exe
Found: C:\cygwin64\bin\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin64\bin\grep.exe
Found: C:\cygwin64\bin\grep.exe
Found: C:\cygwin64\bin\kill.exe
Found: C:\cygwin64\bin\kill.exe
Found: C:\cygwin64\bin\ld.exe
Found: C:\cygwin64\bin\ld.exe
Found: C:\cygwin64\bin\ls.exe
Found: C:\cygwin64\bin\ls.exe
Not Found: make
Found: C:\cygwin64\bin\mv.exe
Found: C:\cygwin64\bin\mv.exe
Not Found: patch
Found: C:\cygwin64\bin\perl.exe
Found: C:\cygwin64\bin\perl.exe
Found: C:\cygwin64\bin\rm.exe
Found: C:\cygwin64\bin\rm.exe
Found: C:\cygwin64\bin\sed.exe
Found: C:\cygwin64\bin\sed.exe
Not Found: ssh
Found: C:\cygwin64\bin\sh.exe
Found: C:\cygwin64\bin\sh.exe
Found: C:\cygwin64\bin\tar.exe
Found: C:\cygwin64\bin\tar.exe
Found: C:\cygwin64\bin\test.exe
Found: C:\cygwin64\bin\test.exe
Found: C:\cygwin64\bin\vi.exe
Found: C:\cygwin64\bin\vi.exe
Not Found: vim
39k 2016/09/19 C:\cygwin64\bin\cygargp-0.dll - os=4.0 img=0.0 sys=5.2
"cygargp-0.dll" v0.0 ts=2016-09-18 21:13
16k 2013/03/26 C:\cygwin64\bin\cygattr-1.dll - os=4.0 img=0.0 sys=5.2
"cygattr-1.dll" v0.0 ts=2013-03-26 13:26
180k 2015/03/23 C:\cygwin64\bin\cygblkid-1.dll - os=4.0 img=0.0 sys=5.2
"cygblkid-1.dll" v0.0 ts=2015-03-23 04:46
64k 2017/02/22 C:\cygwin64\bin\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2
"cygbz2-1.dll" v0.0 ts=2017-02-22 02:22
13k 2015/03/19 C:\cygwin64\bin\cygcom_err-2.dll - os=4.0 img=0.0 sys=5.2
"cygcom_err-2.dll" v0.0 ts=2015-03-18 21:44
10k 2016/06/09 C:\cygwin64\bin\cygcrypt-0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypt-0.dll" v0.0 ts=2016-06-09 11:02
2235k 2017/01/26 C:\cygwin64\bin\cygcrypto-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypto-1.0.0.dll" v0.0 ts=2017-01-26 15:10
485k 2017/06/18 C:\cygwin64\bin\cygcurl-4.dll - os=4.0 img=0.0 sys=5.2
"cygcurl-4.dll" v0.0 ts=2017-06-18 17:01
1549k 2016/08/22 C:\cygwin64\bin\cygdb-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb-5.3.dll" v0.0 ts=2016-08-22 04:51
124k 2016/08/22 C:\cygwin64\bin\cygdb_cxx-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_cxx-5.3.dll" v0.0 ts=2016-08-22 04:52
570k 2016/08/22 C:\cygwin64\bin\cygdb_sql-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_sql-5.3.dll" v0.0 ts=2016-08-22 04:52
148k 2017/08/06 C:\cygwin64\bin\cygexpat-1.dll - os=4.0 img=0.0 sys=5.2
"cygexpat-1.dll" v0.0 ts=2017-08-06 19:43
27k 2015/11/17 C:\cygwin64\bin\cygffi-6.dll - os=4.0 img=0.0 sys=5.2
"cygffi-6.dll" v0.0 ts=2015-11-17 17:14
243k 2016/08/11 C:\cygwin64\bin\cygfontconfig-1.dll - os=4.0 img=0.0 sys=5.2
"cygfontconfig-1.dll" v0.0 ts=2016-08-10 21:54
55k 2017/06/18 C:\cygwin64\bin\cygformw-10.dll - os=4.0 img=0.0 sys=5.2
"cygformw-10.dll" v0.0 ts=2017-06-18 17:23
430k 2017/04/30 C:\cygwin64\bin\cygfreebl3.dll - os=4.0 img=0.0 sys=5.2
"cygfreebl3.dll" v0.0 ts=2017-04-30 16:05
597k 2016/07/28 C:\cygwin64\bin\cygfreetype-6.dll - os=4.0 img=0.0 sys=5.2
"cygfreetype-6.dll" v0.0 ts=2016-07-28 12:48
70k 2016/06/13 C:\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
"cyggcc_s-seh-1.dll" v0.0 ts=2016-06-13 11:18
39k 2016/10/10 C:\cygwin64\bin\cyggdbm-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm-4.dll" v0.0 ts=2016-10-10 04:26
13k 2016/10/10 C:\cygwin64\bin\cyggdbm_compat-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm_compat-4.dll" v0.0 ts=2016-10-10 04:26
527k 2017/01/21 C:\cygwin64\bin\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2
"cyggmp-10.dll" v0.0 ts=2017-01-21 13:25
258k 2016/09/26 C:\cygwin64\bin\cyggssapi_krb5-2.dll - os=4.0 img=0.0 sys=5.2
"cyggssapi_krb5-2.dll" v0.0 ts=2016-09-26 01:55
33k 2017/02/13 C:\cygwin64\bin\cyghistory7.dll - os=4.0 img=0.0 sys=5.2
"cyghistory7.dll" v0.0 ts=2017-02-11 17:39
1009k 2015/02/20 C:\cygwin64\bin\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2
"cygiconv-2.dll" v0.0 ts=2015-02-20 12:07
197k 2017/05/02 C:\cygwin64\bin\cygidn-11.dll - os=4.0 img=0.0 sys=5.2
"cygidn-11.dll" v0.0 ts=2017-05-01 20:18
111k 2017/07/05 C:\cygwin64\bin\cygidn2-0.dll - os=4.0 img=0.0 sys=5.2
"cygidn2-0.dll" v0.0 ts=2017-07-04 20:12
42k 2016/10/23 C:\cygwin64\bin\cygintl-8.dll - os=4.0 img=0.0 sys=5.2
"cygintl-8.dll" v0.0 ts=2016-10-23 02:17
48k 2014/06/17 C:\cygwin64\bin\cygjbig-2.dll - os=4.0 img=0.0 sys=5.2
"cygjbig-2.dll" v0.0 ts=1969-12-31 19:00
18k 2014/06/17 C:\cygwin64\bin\cygjbig85-2.dll - os=4.0 img=0.0 sys=5.2
"cygjbig85-2.dll" v0.0 ts=1969-12-31 19:00
403k 2016/08/07 C:\cygwin64\bin\cygjpeg-8.dll - os=4.0 img=0.0 sys=5.2
"cygjpeg-8.dll" v0.0 ts=2016-08-07 15:20
177k 2016/09/26 C:\cygwin64\bin\cygk5crypto-3.dll - os=4.0 img=0.0 sys=5.2
"cygk5crypto-3.dll" v0.0 ts=2016-09-26 01:55
722k 2016/09/26 C:\cygwin64\bin\cygkrb5-3.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5-3.dll" v0.0 ts=2016-09-26 01:55
35k 2016/09/26 C:\cygwin64\bin\cygkrb5support-0.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5support-0.dll" v0.0 ts=2016-09-26 01:54
45k 2015/11/19 C:\cygwin64\bin\cyglber-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cyglber-2-4-2.dll" v0.0 ts=2015-11-19 09:17
299k 2017/01/03 C:\cygwin64\bin\cyglcms2-2.dll - os=4.0 img=0.0 sys=5.2
"cyglcms2-2.dll" v0.0 ts=2017-01-03 07:40
246k 2015/11/19 C:\cygwin64\bin\cygldap-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap-2-4-2.dll" v0.0 ts=2015-11-19 09:18
262k 2015/11/19 C:\cygwin64\bin\cygldap_r-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap_r-2-4-2.dll" v0.0 ts=2015-11-19 09:19
6k 2017/07/12 C:\cygwin64\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
"cyglsa64.dll" v0.0 ts=2017-07-12 04:58
139k 2017/05/10 C:\cygwin64\bin\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2
"cyglzma-5.dll" v0.0 ts=2017-05-09 20:17
121k 2017/05/03 C:\cygwin64\bin\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2
"cygmagic-1.dll" v0.0 ts=2017-05-03 13:25
169k 2016/10/10 C:\cygwin64\bin\cygman-2-7-5.dll - os=4.0 img=0.0 sys=5.2
"cygman-2-7-5.dll" v0.0 ts=2016-10-10 17:07
22k 2016/10/10 C:\cygwin64\bin\cygmandb-2-7-5.dll - os=4.0 img=0.0 sys=5.2
"cygmandb-2-7-5.dll" v0.0 ts=2016-10-10 17:07
155k 2013/05/29 C:\cygwin64\bin\cygmcrypt-4.dll - os=4.0 img=0.0 sys=5.2
"cygmcrypt-4.dll" v0.0 ts=2013-05-29 09:09
29k 2017/06/18 C:\cygwin64\bin\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2
"cygmenuw-10.dll" v0.0 ts=2017-06-18 17:22
163k 2013/05/29 C:\cygwin64\bin\cygmhash-2.dll - os=4.0 img=0.0 sys=5.2
"cygmhash-2.dll" v0.0 ts=2013-05-29 18:29
346k 2017/08/01 C:\cygwin64\bin\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2
"cygmpfr-4.dll" v0.0 ts=2017-08-01 15:24
53k 2017/06/18 C:\cygwin64\bin\cygncurses++w-10.dll - os=4.0 img=0.0 sys=5.2
"cygncurses++w-10.dll" v0.0 ts=2017-06-18 17:34
288k 2017/06/18 C:\cygwin64\bin\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2
"cygncursesw-10.dll" v0.0 ts=2017-06-18 17:19
138k 2017/06/18 C:\cygwin64\bin\cygnghttp2-14.dll - os=4.0 img=0.0 sys=5.2
"cygnghttp2-14.dll" v0.0 ts=2017-06-18 15:48
222k 2017/04/30 C:\cygwin64\bin\cygnspr4.dll - os=4.0 img=0.0 sys=5.2
"cygnspr4.dll" v0.0 ts=2017-04-30 02:52
1291k 2017/04/30 C:\cygwin64\bin\cygnss3.dll - os=4.0 img=0.0 sys=5.2
"cygnss3.dll" v0.0 ts=2017-04-30 16:07
165k 2017/04/30 C:\cygwin64\bin\cygnssdbm3.dll - os=4.0 img=0.0 sys=5.2
"cygnssdbm3.dll" v0.0 ts=2017-04-30 16:05
154k 2017/04/30 C:\cygwin64\bin\cygnssutil3.dll - os=4.0 img=0.0 sys=5.2
"cygnssutil3.dll" v0.0 ts=2017-04-30 16:04
189k 2016/11/10 C:\cygwin64\bin\cygopenjp2-7.dll - os=4.0 img=2.1 sys=5.2
"cygopenjp2-7.dll" v0.0 ts=2016-11-09 23:24
126k 2016/03/04 C:\cygwin64\bin\cygopenjpeg-1.dll - os=4.0 img=1.5 sys=5.2
"cygopenjpeg-1.dll" v0.0 ts=2016-03-04 11:09
1003k 2017/04/28 C:\cygwin64\bin\cygp11-kit-0.dll - os=4.0 img=0.0 sys=5.2
"cygp11-kit-0.dll" v0.0 ts=2017-04-28 00:23
14k 2017/06/18 C:\cygwin64\bin\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2
"cygpanelw-10.dll" v0.0 ts=2017-06-18 17:21
475k 2017/04/23 C:\cygwin64\bin\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2
"cygpcre-1.dll" v0.0 ts=2017-04-23 19:50
2021k 2017/07/15 C:\cygwin64\bin\cygperl5_22.dll - os=4.0 img=0.0 sys=5.2
"cygperl5_22.dll" v0.0 ts=2017-07-15 14:12
39k 2015/04/09 C:\cygwin64\bin\cygpipeline-1.dll - os=4.0 img=0.0 sys=5.2
"cygpipeline-1.dll" v0.0 ts=2015-04-09 16:04
17k 2017/04/30 C:\cygwin64\bin\cygplc4.dll - os=4.0 img=0.0 sys=5.2
"cygplc4.dll" v0.0 ts=2017-04-30 02:52
14k 2017/04/30 C:\cygwin64\bin\cygplds4.dll - os=4.0 img=0.0 sys=5.2
"cygplds4.dll" v0.0 ts=2017-04-30 02:52
179k 2017/07/10 C:\cygwin64\bin\cygpng16-16.dll - os=4.0 img=0.0 sys=5.2
"cygpng16-16.dll" v0.0 ts=2017-07-10 09:05
2028k 2016/11/10 C:\cygwin64\bin\cygpoppler-62.dll - os=4.0 img=0.0 sys=5.2
"cygpoppler-62.dll" v0.0 ts=2016-11-10 04:04
2044k 2017/04/03 C:\cygwin64\bin\cygpoppler-66.dll - os=4.0 img=0.0 sys=5.2
"cygpoppler-66.dll" v0.0 ts=2017-04-03 03:05
59k 2017/04/03 C:\cygwin64\bin\cygpoppler-cpp-0.dll - os=4.0 img=0.0 sys=5.2
"cygpoppler-cpp-0.dll" v0.0 ts=2017-04-03 03:11
41k 2016/07/13 C:\cygwin64\bin\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2
"cygpopt-0.dll" v0.0 ts=2016-07-13 01:16
52k 2017/01/17 C:\cygwin64\bin\cygpsl-5.dll - os=4.0 img=0.0 sys=5.2
"cygpsl-5.dll" v0.0 ts=2017-01-17 12:10
219k 2017/02/13 C:\cygwin64\bin\cygreadline7.dll - os=4.0 img=0.0 sys=5.2
"cygreadline7.dll" v0.0 ts=2017-02-11 17:39
96k 2017/04/16 C:\cygwin64\bin\cygsasl2-3.dll - os=4.0 img=0.0 sys=5.2
"cygsasl2-3.dll" v0.0 ts=2017-04-16 14:15
11k 2015/07/17 C:\cygwin64\bin\cygsigsegv-2.dll - os=4.0 img=0.0 sys=5.2
"cygsigsegv-2.dll" v0.0 ts=2015-07-17 17:35
89k 2015/03/23 C:\cygwin64\bin\cygsmartcols-1.dll - os=4.0 img=0.0 sys=5.2
"cygsmartcols-1.dll" v0.0 ts=2015-03-23 04:46
167k 2017/04/30 C:\cygwin64\bin\cygsmime3.dll - os=4.0 img=0.0 sys=5.2
"cygsmime3.dll" v0.0 ts=2017-04-30 16:08
263k 2017/04/30 C:\cygwin64\bin\cygsoftokn3.dll - os=4.0 img=0.0 sys=5.2
"cygsoftokn3.dll" v0.0 ts=2017-04-30 16:05
993k 2017/07/06 C:\cygwin64\bin\cygsqlite3-0.dll - os=4.0 img=0.0 sys=5.2
"cygsqlite3-0.dll" v0.0 ts=2017-07-06 04:21
156k 2016/03/02 C:\cygwin64\bin\cygssh2-1.dll - os=4.0 img=0.0 sys=5.2
"cygssh2-1.dll" v0.0 ts=2016-03-02 13:03
399k 2017/01/26 C:\cygwin64\bin\cygssl-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygssl-1.0.0.dll" v0.0 ts=2017-01-26 15:10
360k 2017/04/30 C:\cygwin64\bin\cygssl3.dll - os=4.0 img=0.0 sys=5.2
"cygssl3.dll" v0.0 ts=2017-04-30 16:07
12k 2016/06/13 C:\cygwin64\bin\cygssp-0.dll - os=4.0 img=0.0 sys=5.2
"cygssp-0.dll" v0.0 ts=2016-06-13 12:10
1325k 2016/06/13 C:\cygwin64\bin\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2
"cygstdc++-6.dll" v0.0 ts=2016-06-13 11:38
66k 2017/05/29 C:\cygwin64\bin\cygtasn1-6.dll - os=4.0 img=0.0 sys=5.2
"cygtasn1-6.dll" v0.0 ts=2017-05-29 18:32
54k 2017/06/18 C:\cygwin64\bin\cygticw-10.dll - os=4.0 img=0.0 sys=5.2
"cygticw-10.dll" v0.0 ts=2017-06-18 17:19
420k 2017/05/17 C:\cygwin64\bin\cygtiff-6.dll - os=4.0 img=0.0 sys=5.2
"cygtiff-6.dll" v0.0 ts=2017-05-16 23:57
11k 2017/05/17 C:\cygwin64\bin\cygtiffxx-6.dll - os=4.0 img=0.0 sys=5.2
"cygtiffxx-6.dll" v0.0 ts=2017-05-16 23:57
1538k 2015/10/16 C:\cygwin64\bin\cygunistring-2.dll - os=4.0 img=0.0 sys=5.2
"cygunistring-2.dll" v0.0 ts=2015-10-16 16:40
15k 2015/03/23 C:\cygwin64\bin\cyguuid-1.dll - os=4.0 img=0.0 sys=5.2
"cyguuid-1.dll" v0.0 ts=2015-03-23 04:46
83k 2017/03/03 C:\cygwin64\bin\cygz.dll - os=4.0 img=0.0 sys=5.2
"cygz.dll" v0.0 ts=2017-03-03 16:42
3241k 2017/07/12 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2
"cygwin1.dll" v0.0 ts=2017-07-12 04:58
Cygwin DLL version info:
DLL version: 2.8.2
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 313
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
39k 2016/09/19 C:\cygwin64\bin\cygargp-0.dll - os=4.0 img=0.0 sys=5.2
"cygargp-0.dll" v0.0 ts=2016-09-18 21:13
16k 2013/03/26 C:\cygwin64\bin\cygattr-1.dll - os=4.0 img=0.0 sys=5.2
"cygattr-1.dll" v0.0 ts=2013-03-26 13:26
180k 2015/03/23 C:\cygwin64\bin\cygblkid-1.dll - os=4.0 img=0.0 sys=5.2
"cygblkid-1.dll" v0.0 ts=2015-03-23 04:46
64k 2017/02/22 C:\cygwin64\bin\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2
"cygbz2-1.dll" v0.0 ts=2017-02-22 02:22
13k 2015/03/19 C:\cygwin64\bin\cygcom_err-2.dll - os=4.0 img=0.0 sys=5.2
"cygcom_err-2.dll" v0.0 ts=2015-03-18 21:44
10k 2016/06/09 C:\cygwin64\bin\cygcrypt-0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypt-0.dll" v0.0 ts=2016-06-09 11:02
2235k 2017/01/26 C:\cygwin64\bin\cygcrypto-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypto-1.0.0.dll" v0.0 ts=2017-01-26 15:10
485k 2017/06/18 C:\cygwin64\bin\cygcurl-4.dll - os=4.0 img=0.0 sys=5.2
"cygcurl-4.dll" v0.0 ts=2017-06-18 17:01
1549k 2016/08/22 C:\cygwin64\bin\cygdb-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb-5.3.dll" v0.0 ts=2016-08-22 04:51
124k 2016/08/22 C:\cygwin64\bin\cygdb_cxx-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_cxx-5.3.dll" v0.0 ts=2016-08-22 04:52
570k 2016/08/22 C:\cygwin64\bin\cygdb_sql-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_sql-5.3.dll" v0.0 ts=2016-08-22 04:52
148k 2017/08/06 C:\cygwin64\bin\cygexpat-1.dll - os=4.0 img=0.0 sys=5.2
"cygexpat-1.dll" v0.0 ts=2017-08-06 19:43
27k 2015/11/17 C:\cygwin64\bin\cygffi-6.dll - os=4.0 img=0.0 sys=5.2
"cygffi-6.dll" v0.0 ts=2015-11-17 17:14
243k 2016/08/11 C:\cygwin64\bin\cygfontconfig-1.dll - os=4.0 img=0.0 sys=5.2
"cygfontconfig-1.dll" v0.0 ts=2016-08-10 21:54
55k 2017/06/18 C:\cygwin64\bin\cygformw-10.dll - os=4.0 img=0.0 sys=5.2
"cygformw-10.dll" v0.0 ts=2017-06-18 17:23
430k 2017/04/30 C:\cygwin64\bin\cygfreebl3.dll - os=4.0 img=0.0 sys=5.2
"cygfreebl3.dll" v0.0 ts=2017-04-30 16:05
597k 2016/07/28 C:\cygwin64\bin\cygfreetype-6.dll - os=4.0 img=0.0 sys=5.2
"cygfreetype-6.dll" v0.0 ts=2016-07-28 12:48
70k 2016/06/13 C:\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
"cyggcc_s-seh-1.dll" v0.0 ts=2016-06-13 11:18
39k 2016/10/10 C:\cygwin64\bin\cyggdbm-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm-4.dll" v0.0 ts=2016-10-10 04:26
13k 2016/10/10 C:\cygwin64\bin\cyggdbm_compat-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm_compat-4.dll" v0.0 ts=2016-10-10 04:26
527k 2017/01/21 C:\cygwin64\bin\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2
"cyggmp-10.dll" v0.0 ts=2017-01-21 13:25
258k 2016/09/26 C:\cygwin64\bin\cyggssapi_krb5-2.dll - os=4.0 img=0.0 sys=5.2
"cyggssapi_krb5-2.dll" v0.0 ts=2016-09-26 01:55
33k 2017/02/13 C:\cygwin64\bin\cyghistory7.dll - os=4.0 img=0.0 sys=5.2
"cyghistory7.dll" v0.0 ts=2017-02-11 17:39
1009k 2015/02/20 C:\cygwin64\bin\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2
"cygiconv-2.dll" v0.0 ts=2015-02-20 12:07
197k 2017/05/02 C:\cygwin64\bin\cygidn-11.dll - os=4.0 img=0.0 sys=5.2
"cygidn-11.dll" v0.0 ts=2017-05-01 20:18
111k 2017/07/05 C:\cygwin64\bin\cygidn2-0.dll - os=4.0 img=0.0 sys=5.2
"cygidn2-0.dll" v0.0 ts=2017-07-04 20:12
42k 2016/10/23 C:\cygwin64\bin\cygintl-8.dll - os=4.0 img=0.0 sys=5.2
"cygintl-8.dll" v0.0 ts=2016-10-23 02:17
48k 2014/06/17 C:\cygwin64\bin\cygjbig-2.dll - os=4.0 img=0.0 sys=5.2
"cygjbig-2.dll" v0.0 ts=1969-12-31 19:00
18k 2014/06/17 C:\cygwin64\bin\cygjbig85-2.dll - os=4.0 img=0.0 sys=5.2
"cygjbig85-2.dll" v0.0 ts=1969-12-31 19:00
403k 2016/08/07 C:\cygwin64\bin\cygjpeg-8.dll - os=4.0 img=0.0 sys=5.2
"cygjpeg-8.dll" v0.0 ts=2016-08-07 15:20
177k 2016/09/26 C:\cygwin64\bin\cygk5crypto-3.dll - os=4.0 img=0.0 sys=5.2
"cygk5crypto-3.dll" v0.0 ts=2016-09-26 01:55
722k 2016/09/26 C:\cygwin64\bin\cygkrb5-3.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5-3.dll" v0.0 ts=2016-09-26 01:55
35k 2016/09/26 C:\cygwin64\bin\cygkrb5support-0.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5support-0.dll" v0.0 ts=2016-09-26 01:54
45k 2015/11/19 C:\cygwin64\bin\cyglber-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cyglber-2-4-2.dll" v0.0 ts=2015-11-19 09:17
299k 2017/01/03 C:\cygwin64\bin\cyglcms2-2.dll - os=4.0 img=0.0 sys=5.2
"cyglcms2-2.dll" v0.0 ts=2017-01-03 07:40
246k 2015/11/19 C:\cygwin64\bin\cygldap-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap-2-4-2.dll" v0.0 ts=2015-11-19 09:18
262k 2015/11/19 C:\cygwin64\bin\cygldap_r-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap_r-2-4-2.dll" v0.0 ts=2015-11-19 09:19
6k 2017/07/12 C:\cygwin64\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
"cyglsa64.dll" v0.0 ts=2017-07-12 04:58
139k 2017/05/10 C:\cygwin64\bin\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2
"cyglzma-5.dll" v0.0 ts=2017-05-09 20:17
121k 2017/05/03 C:\cygwin64\bin\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2
"cygmagic-1.dll" v0.0 ts=2017-05-03 13:25
169k 2016/10/10 C:\cygwin64\bin\cygman-2-7-5.dll - os=4.0 img=0.0 sys=5.2
"cygman-2-7-5.dll" v0.0 ts=2016-10-10 17:07
22k 2016/10/10 C:\cygwin64\bin\cygmandb-2-7-5.dll - os=4.0 img=0.0 sys=5.2
"cygmandb-2-7-5.dll" v0.0 ts=2016-10-10 17:07
155k 2013/05/29 C:\cygwin64\bin\cygmcrypt-4.dll - os=4.0 img=0.0 sys=5.2
"cygmcrypt-4.dll" v0.0 ts=2013-05-29 09:09
29k 2017/06/18 C:\cygwin64\bin\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2
"cygmenuw-10.dll" v0.0 ts=2017-06-18 17:22
163k 2013/05/29 C:\cygwin64\bin\cygmhash-2.dll - os=4.0 img=0.0 sys=5.2
"cygmhash-2.dll" v0.0 ts=2013-05-29 18:29
346k 2017/08/01 C:\cygwin64\bin\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2
"cygmpfr-4.dll" v0.0 ts=2017-08-01 15:24
53k 2017/06/18 C:\cygwin64\bin\cygncurses++w-10.dll - os=4.0 img=0.0 sys=5.2
"cygncurses++w-10.dll" v0.0 ts=2017-06-18 17:34
288k 2017/06/18 C:\cygwin64\bin\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2
"cygncursesw-10.dll" v0.0 ts=2017-06-18 17:19
138k 2017/06/18 C:\cygwin64\bin\cygnghttp2-14.dll - os=4.0 img=0.0 sys=5.2
"cygnghttp2-14.dll" v0.0 ts=2017-06-18 15:48
222k 2017/04/30 C:\cygwin64\bin\cygnspr4.dll - os=4.0 img=0.0 sys=5.2
"cygnspr4.dll" v0.0 ts=2017-04-30 02:52
1291k 2017/04/30 C:\cygwin64\bin\cygnss3.dll - os=4.0 img=0.0 sys=5.2
"cygnss3.dll" v0.0 ts=2017-04-30 16:07
165k 2017/04/30 C:\cygwin64\bin\cygnssdbm3.dll - os=4.0 img=0.0 sys=5.2
"cygnssdbm3.dll" v0.0 ts=2017-04-30 16:05
154k 2017/04/30 C:\cygwin64\bin\cygnssutil3.dll - os=4.0 img=0.0 sys=5.2
"cygnssutil3.dll" v0.0 ts=2017-04-30 16:04
189k 2016/11/10 C:\cygwin64\bin\cygopenjp2-7.dll - os=4.0 img=2.1 sys=5.2
"cygopenjp2-7.dll" v0.0 ts=2016-11-09 23:24
126k 2016/03/04 C:\cygwin64\bin\cygopenjpeg-1.dll - os=4.0 img=1.5 sys=5.2
"cygopenjpeg-1.dll" v0.0 ts=2016-03-04 11:09
1003k 2017/04/28 C:\cygwin64\bin\cygp11-kit-0.dll - os=4.0 img=0.0 sys=5.2
"cygp11-kit-0.dll" v0.0 ts=2017-04-28 00:23
14k 2017/06/18 C:\cygwin64\bin\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2
"cygpanelw-10.dll" v0.0 ts=2017-06-18 17:21
475k 2017/04/23 C:\cygwin64\bin\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2
"cygpcre-1.dll" v0.0 ts=2017-04-23 19:50
2021k 2017/07/15 C:\cygwin64\bin\cygperl5_22.dll - os=4.0 img=0.0 sys=5.2
"cygperl5_22.dll" v0.0 ts=2017-07-15 14:12
39k 2015/04/09 C:\cygwin64\bin\cygpipeline-1.dll - os=4.0 img=0.0 sys=5.2
"cygpipeline-1.dll" v0.0 ts=2015-04-09 16:04
17k 2017/04/30 C:\cygwin64\bin\cygplc4.dll - os=4.0 img=0.0 sys=5.2
"cygplc4.dll" v0.0 ts=2017-04-30 02:52
14k 2017/04/30 C:\cygwin64\bin\cygplds4.dll - os=4.0 img=0.0 sys=5.2
"cygplds4.dll" v0.0 ts=2017-04-30 02:52
179k 2017/07/10 C:\cygwin64\bin\cygpng16-16.dll - os=4.0 img=0.0 sys=5.2
"cygpng16-16.dll" v0.0 ts=2017-07-10 09:05
2028k 2016/11/10 C:\cygwin64\bin\cygpoppler-62.dll - os=4.0 img=0.0 sys=5.2
"cygpoppler-62.dll" v0.0 ts=2016-11-10 04:04
2044k 2017/04/03 C:\cygwin64\bin\cygpoppler-66.dll - os=4.0 img=0.0 sys=5.2
"cygpoppler-66.dll" v0.0 ts=2017-04-03 03:05
59k 2017/04/03 C:\cygwin64\bin\cygpoppler-cpp-0.dll - os=4.0 img=0.0 sys=5.2
"cygpoppler-cpp-0.dll" v0.0 ts=2017-04-03 03:11
41k 2016/07/13 C:\cygwin64\bin\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2
"cygpopt-0.dll" v0.0 ts=2016-07-13 01:16
52k 2017/01/17 C:\cygwin64\bin\cygpsl-5.dll - os=4.0 img=0.0 sys=5.2
"cygpsl-5.dll" v0.0 ts=2017-01-17 12:10
219k 2017/02/13 C:\cygwin64\bin\cygreadline7.dll - os=4.0 img=0.0 sys=5.2
"cygreadline7.dll" v0.0 ts=2017-02-11 17:39
96k 2017/04/16 C:\cygwin64\bin\cygsasl2-3.dll - os=4.0 img=0.0 sys=5.2
"cygsasl2-3.dll" v0.0 ts=2017-04-16 14:15
11k 2015/07/17 C:\cygwin64\bin\cygsigsegv-2.dll - os=4.0 img=0.0 sys=5.2
"cygsigsegv-2.dll" v0.0 ts=2015-07-17 17:35
89k 2015/03/23 C:\cygwin64\bin\cygsmartcols-1.dll - os=4.0 img=0.0 sys=5.2
"cygsmartcols-1.dll" v0.0 ts=2015-03-23 04:46
167k 2017/04/30 C:\cygwin64\bin\cygsmime3.dll - os=4.0 img=0.0 sys=5.2
"cygsmime3.dll" v0.0 ts=2017-04-30 16:08
263k 2017/04/30 C:\cygwin64\bin\cygsoftokn3.dll - os=4.0 img=0.0 sys=5.2
"cygsoftokn3.dll" v0.0 ts=2017-04-30 16:05
993k 2017/07/06 C:\cygwin64\bin\cygsqlite3-0.dll - os=4.0 img=0.0 sys=5.2
"cygsqlite3-0.dll" v0.0 ts=2017-07-06 04:21
156k 2016/03/02 C:\cygwin64\bin\cygssh2-1.dll - os=4.0 img=0.0 sys=5.2
"cygssh2-1.dll" v0.0 ts=2016-03-02 13:03
399k 2017/01/26 C:\cygwin64\bin\cygssl-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygssl-1.0.0.dll" v0.0 ts=2017-01-26 15:10
360k 2017/04/30 C:\cygwin64\bin\cygssl3.dll - os=4.0 img=0.0 sys=5.2
"cygssl3.dll" v0.0 ts=2017-04-30 16:07
12k 2016/06/13 C:\cygwin64\bin\cygssp-0.dll - os=4.0 img=0.0 sys=5.2
"cygssp-0.dll" v0.0 ts=2016-06-13 12:10
1325k 2016/06/13 C:\cygwin64\bin\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2
"cygstdc++-6.dll" v0.0 ts=2016-06-13 11:38
66k 2017/05/29 C:\cygwin64\bin\cygtasn1-6.dll - os=4.0 img=0.0 sys=5.2
"cygtasn1-6.dll" v0.0 ts=2017-05-29 18:32
54k 2017/06/18 C:\cygwin64\bin\cygticw-10.dll - os=4.0 img=0.0 sys=5.2
"cygticw-10.dll" v0.0 ts=2017-06-18 17:19
420k 2017/05/17 C:\cygwin64\bin\cygtiff-6.dll - os=4.0 img=0.0 sys=5.2
"cygtiff-6.dll" v0.0 ts=2017-05-16 23:57
11k 2017/05/17 C:\cygwin64\bin\cygtiffxx-6.dll - os=4.0 img=0.0 sys=5.2
"cygtiffxx-6.dll" v0.0 ts=2017-05-16 23:57
1538k 2015/10/16 C:\cygwin64\bin\cygunistring-2.dll - os=4.0 img=0.0 sys=5.2
"cygunistring-2.dll" v0.0 ts=2015-10-16 16:40
15k 2015/03/23 C:\cygwin64\bin\cyguuid-1.dll - os=4.0 img=0.0 sys=5.2
"cyguuid-1.dll" v0.0 ts=2015-03-23 04:46
83k 2017/03/03 C:\cygwin64\bin\cygz.dll - os=4.0 img=0.0 sys=5.2
"cygz.dll" v0.0 ts=2017-03-03 16:42
3241k 2017/07/12 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2
"cygwin1.dll" v0.0 ts=2017-07-12 04:58
Cygwin DLL version info:
DLL version: 2.8.2
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 313
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
Can't find the cygrunsrv utility, skipping services check.
Cygwin Package Information
Last downloaded files to: c:\cygwindownloads
Last downloaded files from: http://mirror.csclub.uwaterloo.ca/cygwin/
Package Version Status
_autorebase 001006-1 OK
alternatives 1.3.30c-10 OK
ascii 3.15-1 OK
attr 2.4.46-1 OK
base-cygwin 3.8-1 OK
base-files 4.2-4 OK
bash 4.4.12-3 OK
bc 1.06.95-2 OK
binutils 2.25-4 OK
bvi 1.3.2-3 OK
bzip2 1.0.6-3 OK
ca-certificates 2.14-1 OK
ccrypt 1.10-1 OK
coreutils 8.26-2 OK
cpio 2.11-3 OK
crypt 1.4-1 OK
cygutils 1.4.16-2 OK
cygwin 2.8.2-1 OK
dash 0.5.9.1-1 OK
dateutils 0.4.0-1 OK
dejavu-fonts 2.37-1 OK
diffutils 3.5-2 OK
dos2unix 7.3.5-1 OK
duff 0.5.2-1 OK
ed 1.14.1-1 OK
editrights 1.03-1 OK
fcrackzip 1.0-1 OK
file 5.30-1 OK
findutils 4.6.0-1 OK
gawk 4.1.4-3 OK
getent 2.18.90-4 OK
grep 3.0-2 OK
groff 1.22.3-1 OK
gzip 1.8-1 OK
hexedit 1.2.13-2 OK
hostname 3.13-1 OK
info 6.4-1 OK
ipc-utils 1.0-2 OK
iprint 1.3-1 OK
less 487-1 OK
libargp 20110921-3 OK
libattr1 2.4.46-1 OK
libblkid1 2.25.2-2 OK
libbz2_1 1.0.6-3 OK
libcom_err2 1.42.12-2 OK
libcrypt0 1.4-1 OK
libcurl4 7.54.1-1 OK
libdb5.3 5.3.28-1 OK
libexpat1 2.2.3-1 OK
libffi6 3.2.1-2 OK
libfontconfig-common 2.12.1-1 OK
libfontconfig1 2.12.1-1 OK
libfreetype6 2.6.5-1 OK
libgcc1 5.4.0-1 OK
libgdbm4 1.12-1 OK
libgmp10 6.1.2-1 OK
libgssapi_krb5_2 1.14.4-1 OK
libiconv 1.14-3 OK
libiconv2 1.14-3 OK
libidn11 1.33-1 OK
libidn2_0 2.0.2-1 OK
libintl8 0.19.8.1-2 OK
libjbig2 2.0-14 OK
libjpeg8 1.5.0-1 OK
libk5crypto3 1.14.4-1 OK
libkrb5_3 1.14.4-1 OK
libkrb5support0 1.14.4-1 OK
liblcms2_2 2.8-1 OK
liblzma5 5.2.3-1 OK
libmcrypt4 2.5.8-1 OK
libmhash2 0.9.9.9-2 OK
libmpfr4 3.1.5-1p10 OK
libncursesw10 6.0-11.20170617 OK
libnghttp2_14 1.23.1-1 OK
libnspr4 4.14-1 OK
libnss3 3.30.2-1 OK
libopenjp2_7 2.1.2-1 OK
libopenjpeg1 1.5.2-3 OK
libopenldap2_4_2 2.4.42-1 OK
libopenssl100 1.0.2k-1 OK
libp11-kit0 0.23.5-1 OK
libpcre1 8.40-3 OK
libpipeline1 1.4.0-1 OK
libpng16 1.6.30-2 OK
libpoppler-cpp0 0.52.0-1 OK
libpoppler62 0.45.0-2 OK
libpoppler66 0.52.0-1 OK
libpopt-common 1.16-2 OK
libpopt0 1.16-2 OK
libpsl5 0.17.0-1 OK
libreadline7 7.0.3-3 OK
libsasl2_3 2.1.26-11 OK
libsigsegv2 2.10-2 OK
libsmartcols1 2.25.2-2 OK
libsqlite3_0 3.19.3-1 OK
libssh2_1 1.7.0-1 OK
libssp0 5.4.0-1 OK
libstdc++6 5.4.0-1 OK
libtasn1_6 4.12-1 OK
libtiff6 4.0.7-1 OK
libunistring2 0.9.6-1 OK
libuuid1 2.25.2-2 OK
login 1.11-1 OK
lynx 2.8.7-2 OK
man-db 2.7.5-2 OK
mcrypt 2.6.8-1 OK
mintty 2.7.9-0 OK
mksh 54-1 OK
ncurses 6.0-11.20170617 OK
openssl 1.0.2k-1 OK
p11-kit 0.23.5-1 OK
p11-kit-trust 0.23.5-1 OK
pdfgrep 1.4.1-1 OK
perl 5.22.4-1 OK
perl_autorebase 5.22.4-1 OK
perl_base 5.22.4-1 OK
poppler-data 0.4.7-1 OK
publicsuffix-list-dafsa 20170424-1 OK
rebase 4.4.2-1 OK
rsh 0.17-2 OK
run 1.3.4-2 OK
sed 4.4-1 OK
tar 1.29-1 OK
terminfo 6.0-11.20170617 OK
tftp 5.2-1 OK
tzcode 2016j-1 OK
tzdata 2017b-1 OK
util-linux 2.25.2-2 OK
vim-minimal 8.0.0647-1 OK
which 2.20-2 OK
xz 5.2.3-1 OK
zlib0 1.2.11-1 OK
Use -h to see help about each section
[-- Attachment #3: Type: text/plain, Size: 219 bytes --]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-21 22:30 alias appears to not work inside a called bash script Michel LaBarre
@ 2017-08-21 22:53 ` Eliot Moss
2017-08-21 22:55 ` alias appears to not work inside a called bash scripty Duncan Roe
2017-08-22 14:31 ` alias appears to not work inside a called bash script Stephen John Smoogen
2 siblings, 0 replies; 24+ messages in thread
From: Eliot Moss @ 2017-08-21 22:53 UTC (permalink / raw)
To: cygwin
On 8/21/2017 6:30 PM, Michel LaBarre wrote:
> Hello all,
>
> I have a 4 line bash script:
> #!/bin/bash
> alias nawk=gawk
> alias nawk
> nawk 'BEGIN {FS="^"} ; (length($0) > maxline) { maxline = length($0) ;
> line=$0} ; END{print maxline, line}' $*
>
>
> When I run the script I see:
> alias nawk='gawk'
> /cygdrive/c/mybin/maxline/: line 4: nawk: command not found
>
> It looks like the alias is properly defined but it does not appear to take
> effect.
>
> Same thing happens if I alias to awk instead of qawk.
>
> Same thing happens if I define the alias in .bashrc (I include an echo in
> bashrc to confirm that it is being invoked).
>
> My .bashrc is not likely a factor - I empty it and the result is the same.
> No carriage returns in the script or .bashrc.
>
> I have updated everything August 5th using setup and letting all "Pending"
> pkgs update so I believe I am up to date.
>
> The funny thing is that it works ok from an interactive session, whether the
> alias is explicitly defined in the session or in .bashrc.
From the bash man page:
"Aliases are ot expanded when the shell is not interactive, unless the expand_aliases shell option
is set using shopt (see the description of shopt under SHELL BUILTIN COMMANDS below)."
Could that be the root of your difficulty?
Eliot Moss
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash scripty
2017-08-21 22:30 alias appears to not work inside a called bash script Michel LaBarre
2017-08-21 22:53 ` Eliot Moss
@ 2017-08-21 22:55 ` Duncan Roe
2017-08-22 1:01 ` Michel LaBarre
2017-08-22 14:31 ` alias appears to not work inside a called bash script Stephen John Smoogen
2 siblings, 1 reply; 24+ messages in thread
From: Duncan Roe @ 2017-08-21 22:55 UTC (permalink / raw)
To: cygwin
On Mon, Aug 21, 2017 at 06:30:15PM -0400, Michel LaBarre wrote:
> Hello all,
>
> I have a 4 line bash script:
> #!/bin/bash
> alias nawk=gawk
> alias nawk
> nawk 'BEGIN {FS="^"} ; (length($0) > maxline) { maxline = length($0) ;
> line=$0} ; END{print maxline, line}' $*
>
>
> When I run the script I see:
> alias nawk='gawk'
> /cygdrive/c/mybin/maxline/: line 4: nawk: command not found
>
> It looks like the alias is properly defined but it does not appear to take
> effect.
>
> Same thing happens if I alias to awk instead of qawk.
>
> Same thing happens if I define the alias in .bashrc (I include an echo in
> bashrc to confirm that it is being invoked).
>
> My .bashrc is not likely a factor - I empty it and the result is the same.
> No carriage returns in the script or .bashrc.
>
> I have updated everything August 5th using setup and letting all "Pending"
> pkgs update so I believe I am up to date.
>
> The funny thing is that it works ok from an interactive session, whether the
> alias is explicitly defined in the session or in .bashrc.
>
> Thank you in advance for any insights.
>
> BTW - I just re-subscribed to cygwin 4-5 hours ago and have not seen any
> mail which seems unusual based on past experience.
>
> Michel LaBarre
> 613-692-0507
>
>
This is expected behaviour. "man bash" gibes
" Aliases are not expanded when the shell is not interactive, unless the
expand_aliases shell option is set using shopt (see the description of shopt
under SHELL BUILTIN COMMANDS below).
Cheers ... Duncan.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* RE: alias appears to not work inside a called bash scripty
2017-08-21 22:55 ` alias appears to not work inside a called bash scripty Duncan Roe
@ 2017-08-22 1:01 ` Michel LaBarre
0 siblings, 0 replies; 24+ messages in thread
From: Michel LaBarre @ 2017-08-22 1:01 UTC (permalink / raw)
To: 'Duncan Roe', cygwin, 'Eliot Moss'
Rats! You are right. Thank you so much Duncan and Eliot (both for the
information and the tactful tone :-) ).
I will review shopt - I had been only looking at "set" for relevant
options.
> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of Duncan Roe
> Sent: August-21-17 6:56 PM
> To: cygwin@cygwin.com
> Subject: Re: alias appears to not work inside a called bash scripty
>
> On Mon, Aug 21, 2017 at 06:30:15PM -0400, Michel LaBarre wrote:
> > Hello all,
> >
> > I have a 4 line bash script:
> > #!/bin/bash
> > alias nawk=gawk
> > alias nawk
> > nawk 'BEGIN {FS="^"} ; (length($0) > maxline) { maxline = length($0)
;
> > line=$0} ; END{print maxline, line}' $*
> >
> >
> > When I run the script I see:
> > alias nawk='gawk'
> > /cygdrive/c/mybin/maxline/: line 4: nawk: command not found
> >
> > It looks like the alias is properly defined but it does not appear to
take
> > effect.
> >
> > Same thing happens if I alias to awk instead of qawk.
> >
> > Same thing happens if I define the alias in .bashrc (I include an echo
in
> > bashrc to confirm that it is being invoked).
> >
> > My .bashrc is not likely a factor - I empty it and the result is the
same.
> > No carriage returns in the script or .bashrc.
> >
> > I have updated everything August 5th using setup and letting all
"Pending"
> > pkgs update so I believe I am up to date.
> >
> > The funny thing is that it works ok from an interactive session, whether
the
> > alias is explicitly defined in the session or in .bashrc.
> >
> > Thank you in advance for any insights.
> >
> > BTW - I just re-subscribed to cygwin 4-5 hours ago and have not seen any
> > mail which seems unusual based on past experience.
> >
> > Michel LaBarre
> > 613-692-0507
> >
> >
> This is expected behaviour. "man bash" gibes
>
> " Aliases are not expanded when the shell is not interactive, unless the
> expand_aliases shell option is set using shopt (see the description of
shopt
> under SHELL BUILTIN COMMANDS below).
>
> Cheers ... Duncan.
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-21 22:30 alias appears to not work inside a called bash script Michel LaBarre
2017-08-21 22:53 ` Eliot Moss
2017-08-21 22:55 ` alias appears to not work inside a called bash scripty Duncan Roe
@ 2017-08-22 14:31 ` Stephen John Smoogen
2017-08-22 14:47 ` Eliot Moss
2 siblings, 1 reply; 24+ messages in thread
From: Stephen John Smoogen @ 2017-08-22 14:31 UTC (permalink / raw)
To: cygwin
On 21 August 2017 at 18:30, Michel LaBarre <michel.labarre@rogers.com> wrote:
>
> Hello all,
>
> I have a 4 line bash script:
> #!/bin/bash
> alias nawk=gawk
> alias nawk
> nawk 'BEGIN {FS="^"} ; (length($0) > maxline) { maxline = length($0) ;
> line=$0} ; END{print maxline, line}' $*
>
>
> When I run the script I see:
> alias nawk='gawk'
> /cygdrive/c/mybin/maxline/: line 4: nawk: command not found
>
I replicated this problem on my system and found that the fix is to add a
shopt -s expand_aliases
at the top of the script. I don't know why the option is turned off
when running scripts versus in a plain script but that seems to be a
default in Cygwin.
> It looks like the alias is properly defined but it does not appear to take
> effect.
>
> Same thing happens if I alias to awk instead of qawk.
>
> Same thing happens if I define the alias in .bashrc (I include an echo in
> bashrc to confirm that it is being invoked).
>
> My .bashrc is not likely a factor - I empty it and the result is the same.
> No carriage returns in the script or .bashrc.
>
> I have updated everything August 5th using setup and letting all "Pending"
> pkgs update so I believe I am up to date.
>
> The funny thing is that it works ok from an interactive session, whether the
> alias is explicitly defined in the session or in .bashrc.
>
> Thank you in advance for any insights.
>
> BTW - I just re-subscribed to cygwin 4-5 hours ago and have not seen any
> mail which seems unusual based on past experience.
>
> Michel LaBarre
> 613-692-0507
>
>
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
--
Stephen J Smoogen.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 14:31 ` alias appears to not work inside a called bash script Stephen John Smoogen
@ 2017-08-22 14:47 ` Eliot Moss
2017-08-22 15:19 ` Stephen John Smoogen
0 siblings, 1 reply; 24+ messages in thread
From: Eliot Moss @ 2017-08-22 14:47 UTC (permalink / raw)
To: cygwin
On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
> I replicated this problem on my system and found that the fix is to add a
>
> shopt -s expand_aliases
>
> at the top of the script. I don't know why the option is turned off
> when running scripts versus in a plain script but that seems to be a
> default in Cygwin.
It's a *bash* default - it has nothing to do with Cygwin as distinct
from other bash installations. If you had a different experience
elsewhere, it could be that the default was overridden in some system
wide bashrc file - but that strikes me as unlikely. I suspect that
this is done as a security measure, to prevent an alias from introducing
a surprise.
Regards - EM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 14:47 ` Eliot Moss
@ 2017-08-22 15:19 ` Stephen John Smoogen
2017-08-22 16:46 ` Eliot Moss
2017-08-22 17:08 ` alias appears to not work inside a called bash script cyg Simple
0 siblings, 2 replies; 24+ messages in thread
From: Stephen John Smoogen @ 2017-08-22 15:19 UTC (permalink / raw)
To: moss, cygwin
On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
>
>> I replicated this problem on my system and found that the fix is to add a
>>
>> shopt -s expand_aliases
>>
>> at the top of the script. I don't know why the option is turned off
>> when running scripts versus in a plain script but that seems to be a
>> default in Cygwin.
>
>
> It's a *bash* default - it has nothing to do with Cygwin as distinct
> from other bash installations. If you had a different experience
> elsewhere, it could be that the default was overridden in some system
> wide bashrc file - but that strikes me as unlikely. I suspect that
> this is done as a security measure, to prevent an alias from introducing
> a surprise.
>
I checked on CentOS and there is no shopt option set in any of the
/etc/ files. It must be a compiled in default of some sort as EL6 and
EL7 both work without an explicit `shopt -s expand_aliases`. I then
tried on an Ubuntu 16.04 system and it works without the `shopt -s
expand_aliases` also.
I didn't have access to anything else at the moment so I can't say
which other systems might actually follow the default other than
Cygwin at the moment.
> Regards - EM
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Stephen J Smoogen.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 15:19 ` Stephen John Smoogen
@ 2017-08-22 16:46 ` Eliot Moss
2017-08-22 18:25 ` Stephen John Smoogen
2017-08-22 17:08 ` alias appears to not work inside a called bash script cyg Simple
1 sibling, 1 reply; 24+ messages in thread
From: Eliot Moss @ 2017-08-22 16:46 UTC (permalink / raw)
To: cygwin
On 8/22/2017 11:18 AM, Stephen John Smoogen wrote:
> On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
>> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
>> It's a *bash* default - it has nothing to do with Cygwin as distinct
>> from other bash installations. If you had a different experience
>> elsewhere, it could be that the default was overridden in some system
>> wide bashrc file - but that strikes me as unlikely. I suspect that
>> this is done as a security measure, to prevent an alias from introducing
>> a surprise.
>>
>
> I checked on CentOS and there is no shopt option set in any of the
> /etc/ files. It must be a compiled in default of some sort as EL6 and
> EL7 both work without an explicit `shopt -s expand_aliases`. I then
> tried on an Ubuntu 16.04 system and it works without the `shopt -s
> expand_aliases` also.
>
> I didn't have access to anything else at the moment so I can't say
> which other systems might actually follow the default other than
> Cygwin at the moment.
Hmmm ... One of my servers runs EL7 and it works there exactly as under
Cygwin on my laptop. I wonder: Is there an nawk installed somewhere
on your path on these CentOS and EL* systems? Put another way, if you
put 'type -a nawk' in your script *before* the alias lines, what output
do you get? And what about shopt? I added these lines before the alias
lines:
shopt | grep expand_aliases
type -a nawk
type -t nawk
Regards - Eliot
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 15:19 ` Stephen John Smoogen
2017-08-22 16:46 ` Eliot Moss
@ 2017-08-22 17:08 ` cyg Simple
2017-08-22 17:14 ` Eliot Moss
1 sibling, 1 reply; 24+ messages in thread
From: cyg Simple @ 2017-08-22 17:08 UTC (permalink / raw)
To: cygwin
On 8/22/2017 11:18 AM, Stephen John Smoogen wrote:
> On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
>> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
>>
>>> I replicated this problem on my system and found that the fix is to add a
>>>
>>> shopt -s expand_aliases
>>>
>>> at the top of the script. I don't know why the option is turned off
>>> when running scripts versus in a plain script but that seems to be a
>>> default in Cygwin.
>>
>>
>> It's a *bash* default - it has nothing to do with Cygwin as distinct
>> from other bash installations. If you had a different experience
>> elsewhere, it could be that the default was overridden in some system
>> wide bashrc file - but that strikes me as unlikely. I suspect that
>> this is done as a security measure, to prevent an alias from introducing
>> a surprise.
>>
>
> I checked on CentOS and there is no shopt option set in any of the
> /etc/ files. It must be a compiled in default of some sort as EL6 and
> EL7 both work without an explicit `shopt -s expand_aliases`. I then
> tried on an Ubuntu 16.04 system and it works without the `shopt -s
> expand_aliases` also.
>
> I didn't have access to anything else at the moment so I can't say
> which other systems might actually follow the default other than
> Cygwin at the moment.
Are you talking bash as sh or bash as bash? Bash as sh will expand
those aliases. But you should study
http://tldp.org/LDP/abs/html/aliases.html for all your scripts. Are
there environment variables that could affect the outcome?
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 17:08 ` alias appears to not work inside a called bash script cyg Simple
@ 2017-08-22 17:14 ` Eliot Moss
2017-08-22 19:07 ` cyg Simple
0 siblings, 1 reply; 24+ messages in thread
From: Eliot Moss @ 2017-08-22 17:14 UTC (permalink / raw)
To: cygwin
On 8/22/2017 1:07 PM, cyg Simple wrote:
> On 8/22/2017 11:18 AM, Stephen John Smoogen wrote:
>> On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
>>> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
> Are you talking bash as sh or bash as bash? Bash as sh will expand
> those aliases. But you should study
> http://tldp.org/LDP/abs/html/aliases.html for all your scripts. Are
> there environment variables that could affect the outcome?
Since the OP has a #! /bin/bash line at the top of his script, I think
he means bash. However, running the script with sh explicitly does act
as you describe, e.g.: sh myscript x y z ... in contrast to: myscript x y z.
Regards - EM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 16:46 ` Eliot Moss
@ 2017-08-22 18:25 ` Stephen John Smoogen
2017-08-25 0:37 ` Either trim quoted text or STOP BOTTOM POSTING (was: alias appears to not work...) L A Walsh
0 siblings, 1 reply; 24+ messages in thread
From: Stephen John Smoogen @ 2017-08-22 18:25 UTC (permalink / raw)
To: moss, cygwin
On 22 August 2017 at 12:45, Eliot Moss <moss@cs.umass.edu> wrote:
> On 8/22/2017 11:18 AM, Stephen John Smoogen wrote:
>>
>> On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
>>>
>>> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
>
>
>>> It's a *bash* default - it has nothing to do with Cygwin as distinct
>>> from other bash installations. If you had a different experience
>>> elsewhere, it could be that the default was overridden in some system
>>> wide bashrc file - but that strikes me as unlikely. I suspect that
>>> this is done as a security measure, to prevent an alias from introducing
>>> a surprise.
>>>
>>
>> I checked on CentOS and there is no shopt option set in any of the
>> /etc/ files. It must be a compiled in default of some sort as EL6 and
>> EL7 both work without an explicit `shopt -s expand_aliases`. I then
>> tried on an Ubuntu 16.04 system and it works without the `shopt -s
>> expand_aliases` also.
>>
>> I didn't have access to anything else at the moment so I can't say
>> which other systems might actually follow the default other than
>> Cygwin at the moment.
>
>
> Hmmm ... One of my servers runs EL7 and it works there exactly as under
> Cygwin on my laptop. I wonder: Is there an nawk installed somewhere
> on your path on these CentOS and EL* systems? Put another way, if you
> put 'type -a nawk' in your script *before* the alias lines, what output
> do you get? And what about shopt? I added these lines before the alias
> lines:
>
> shopt | grep expand_aliases
> type -a nawk
> type -t nawk
>
> Regards - Eliot
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
OK I figured it out. I didn't copy the original script correctly.
[ssmoogen@el-7 ~]$ ./x.sh foobar
Before alias
expand_aliases on
./x.sh: line 4: type: nawk: not found
After alias
expand_aliases on
nawk is aliased to `/usr/bin/awk'
alias
Hello World!
[ssmoogen@el-7 ~]$ cat x.sh
#!/bin/sh
echo "Before alias"
shopt | grep expand_aliases
type -a nawk
type -t nawk
alias nawk='/usr/bin/awk'
echo "After alias"
shopt | grep expand_aliases
type -a nawk
type -t nawk
nawk '{print $0}' $*
Change that #!/bin/sh to #!/bin/bash
[ssmoogen@el-7 ~]$ ./x.sh foobar
Before alias
expand_aliases off
./x.sh: line 4: type: nawk: not found
After alias
expand_aliases off
./x.sh: line 9: type: nawk: not found
./x.sh: line 11: nawk: command not found
So when you use bourne sh compatibility aliases get expanded. When you
don't.. they do as the reporter says.
--
Stephen J Smoogen.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 17:14 ` Eliot Moss
@ 2017-08-22 19:07 ` cyg Simple
2017-08-22 19:11 ` cyg Simple
0 siblings, 1 reply; 24+ messages in thread
From: cyg Simple @ 2017-08-22 19:07 UTC (permalink / raw)
To: cygwin
On 8/22/2017 1:13 PM, Eliot Moss wrote:
> On 8/22/2017 1:07 PM, cyg Simple wrote:
>> On 8/22/2017 11:18 AM, Stephen John Smoogen wrote:
>>> On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
>>>> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
>
>> Are you talking bash as sh or bash as bash? Bash as sh will expand
>> those aliases. But you should study
>> http://tldp.org/LDP/abs/html/aliases.html for all your scripts. Are
>> there environment variables that could affect the outcome?
>
> Since the OP has a #! /bin/bash line at the top of his script, I think
> he means bash. However, running the script with sh explicitly does act
> as you describe, e.g.:Â sh myscript x y z ... in contrast to: myscript x
> y z.
>
There's also --posix and set -o posix which will cause bash to perform
as the OP reports. I'm guessing this to be used in the bash startup
files in a global fashion on those systems that you're not having to
specify to use aliases.
https://www.gnu.org/software/bash/manual/html_node/Bash-POSIX-Mode.html#Bash-POSIX-Mode
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 19:07 ` cyg Simple
@ 2017-08-22 19:11 ` cyg Simple
2017-08-23 19:08 ` Eric Blake
0 siblings, 1 reply; 24+ messages in thread
From: cyg Simple @ 2017-08-22 19:11 UTC (permalink / raw)
To: cygwin
On 8/22/2017 3:07 PM, cyg Simple wrote:
> On 8/22/2017 1:13 PM, Eliot Moss wrote:
>> On 8/22/2017 1:07 PM, cyg Simple wrote:
>>> On 8/22/2017 11:18 AM, Stephen John Smoogen wrote:
>>>> On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
>>>>> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
>>
>>> Are you talking bash as sh or bash as bash? Bash as sh will expand
>>> those aliases. But you should study
>>> http://tldp.org/LDP/abs/html/aliases.html for all your scripts. Are
>>> there environment variables that could affect the outcome?
>>
>> Since the OP has a #! /bin/bash line at the top of his script, I think
>> he means bash. However, running the script with sh explicitly does act
>> as you describe, e.g.:Â sh myscript x y z ... in contrast to: myscript x
>> y z.
>>
>
> There's also --posix and set -o posix which will cause bash to perform
> as the OP reports. I'm guessing this to be used in the bash startup
> files in a global fashion on those systems that you're not having to
> specify to use aliases.
>
> https://www.gnu.org/software/bash/manual/html_node/Bash-POSIX-Mode.html#Bash-POSIX-Mode
>
And --enable-strict-posix-default configure option turns this setting on
by default. I'll leave it up to the Cygwin maintainer to decide if it
should be used.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 19:11 ` cyg Simple
@ 2017-08-23 19:08 ` Eric Blake
0 siblings, 0 replies; 24+ messages in thread
From: Eric Blake @ 2017-08-23 19:08 UTC (permalink / raw)
To: cygwin
[-- Attachment #1.1: Type: text/plain, Size: 551 bytes --]
On 08/22/2017 02:11 PM, cyg Simple wrote:
>
> And --enable-strict-posix-default configure option turns this setting on
> by default. I'll leave it up to the Cygwin maintainer to decide if it
> should be used.
It should not. It will break more things than it fixes (running bash as
/bin/sh already implies --posix; that's already close enough without
having to make /bin/bash cripple non-POSIX extensions).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread
* Either trim quoted text or STOP BOTTOM POSTING (was: alias appears to not work...)
2017-08-22 18:25 ` Stephen John Smoogen
@ 2017-08-25 0:37 ` L A Walsh
2017-08-25 14:25 ` Either trim quoted text or STOP BOTTOM POSTING cyg Simple
0 siblings, 1 reply; 24+ messages in thread
From: L A Walsh @ 2017-08-25 0:37 UTC (permalink / raw)
To: cygwin, smooge, moss, michel.labarre, duncan_roe, cygsimple
<forward>
If you can't trim your quoted text, then please stop burying the
new stuff on the bottom.
Some people expect to be able to read every email like a separate
book --- with everything in the topic included in EACH email. This
is just abusive because they demand that everyone put things in
"book" order with newest stuff last.
If you think about it, in normal face-to-face interactions, don't
most people consider it rude when someone jumps into the middle
of a conversation and and wants a people to stop the conversation
and repeat the previous stuff so they can be brought up to speed?
Isn't that a bit wasteful of the groups time?
So why would people think it normal to include all the text from
a thread/subject just so people won't have to read previous emails?
If I enter a thread, and am going to respond to something, I try
to read the previous few notes in the chain to see what is being
responded to.
I've noticed it is most often bottom-poster who include all
previous quotes -- and that's the worst -- having to WADE
through EVERYTHING that came before, when EVERYONE on the
list has already received it. That's the rub: if you
want to bottom-post, then trim what you are quoting to that
which is necessary (and that's fine w/me).
But if you are not good about trimming, then put the *IMPORTANT*
stuff first (your NEW text). That's write -- the most important
thing in your email is what YOU are writing. It should come
first. If you feel a need to quote large parts of the previous
conversation, put it in an appendix -- because most people will
have already received and read it. Including it again is
"superfluous", but that's why there are appendices.
I DO pay attention to the subject BTW.
</forward>
<replytext>
I use aliases in many
of my scripts. I even have an "include" file I use to include
nearly all possible alias I might use, that I can include with:
"include stdalias" (similar to sourcing it, but with enhancements)
But most don't have my 'include' setup (which is slightly complicated),
so for standalone scripts that I might want to export, I'll
put in a short prefix-stanza, like:
shopt -s expand_aliases
alias my=declare array=my\ -a int=my\ -i hash=my\ -A
...rest of script that uses 'my' instead of declare or local (they
are equivalent except local can't be used outside of a 'sub'),
and a few type-specific aliases for int's arrays and hashes,
so I can declare them like:
my foo=bar
int isint=1
hash myhash=([one]=1 [two]=2)
array myarray=(zero one two) # not strictly necessary as
# 'int' and 'hash' are. Showing them using 'my -p':
> my -p foo isint myhash myarray # (shows:)
declare -- foo="bar"
declare -i isint="1"
declare -A myhash=([two]="2" [one]="1" )
declare -a myarray=([0]="zero" [1]="one" [2]="two")
I find they make the code more legible and maintainable.
FWIW, I use BASH_ENV to make sure my aliases are read in, which
uses whether or not 'include' is already defined as an indicator
of whether or not I need to re-read my aliases.sh file (which
defines 'include' as well as my common aliases):
in BASH_ENV:
[[ $(type -t include) == function ]] || source $_LOCAL_DIR_/aliases.sh
</replytext>
-linda
<text type=appendix close=eof>
Stephen John Smoogen wrote:
> On 22 August 2017 at 12:45, Eliot Moss <moss@cs.umass.edu> wrote:
>
>> On 8/22/2017 11:18 AM, Stephen John Smoogen wrote:
>>
>>> On 22 August 2017 at 10:47, Eliot Moss <moss@cs.umass.edu> wrote:
>>>
>>>> On 8/22/2017 10:31 AM, Stephen John Smoogen wrote:
>>>>
>>
>>>> It's a *bash* default - it has nothing to do with Cygwin as distinct
>>>> from other bash installations. If you had a different experience
>>>> elsewhere, it could be that the default was overridden in some system
>>>> wide bashrc file - but that strikes me as unlikely. I suspect that
>>>> this is done as a security measure, to prevent an alias from introducing
>>>> a surprise.
>>>>
>>>>
>>> I checked on CentOS and there is no shopt option set in any of the
>>> /etc/ files. It must be a compiled in default of some sort as EL6 and
>>> EL7 both work without an explicit `shopt -s expand_aliases`. I then
>>> tried on an Ubuntu 16.04 system and it works without the `shopt -s
>>> expand_aliases` also.
>>>
>>> I didn't have access to anything else at the moment so I can't say
>>> which other systems might actually follow the default other than
>>> Cygwin at the moment.
>>>
>> Hmmm ... One of my servers runs EL7 and it works there exactly as under
>> Cygwin on my laptop. I wonder: Is there an nawk installed somewhere
>> on your path on these CentOS and EL* systems? Put another way, if you
>> put 'type -a nawk' in your script *before* the alias lines, what output
>> do you get? And what about shopt? I added these lines before the alias
>> lines:
>>
>> shopt | grep expand_aliases
>> type -a nawk
>> type -t nawk
>>
>> Regards - Eliot
>>
>>
>> --
>> Problem reports: http://cygwin.com/problems.html
>> FAQ: http://cygwin.com/faq/
>> Documentation: http://cygwin.com/docs.html
>> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>>
>>
>
> OK I figured it out. I didn't copy the original script correctly.
>
> [ssmoogen@el-7 ~]$ ./x.sh foobar
> Before alias
> expand_aliases on
> ./x.sh: line 4: type: nawk: not found
> After alias
> expand_aliases on
> nawk is aliased to `/usr/bin/awk'
> alias
> Hello World!
> [ssmoogen@el-7 ~]$ cat x.sh
> #!/bin/sh
> echo "Before alias"
> shopt | grep expand_aliases
> type -a nawk
> type -t nawk
> alias nawk='/usr/bin/awk'
> echo "After alias"
> shopt | grep expand_aliases
> type -a nawk
> type -t nawk
> nawk '{print $0}' $*
>
> Change that #!/bin/sh to #!/bin/bash
>
> [ssmoogen@el-7 ~]$ ./x.sh foobar
> Before alias
> expand_aliases off
> ./x.sh: line 4: type: nawk: not found
> After alias
> expand_aliases off
> ./x.sh: line 9: type: nawk: not found
> ./x.sh: line 11: nawk: command not found
>
> So when you use bourne sh compatibility aliases get expanded. When you
> don't.. they do as the reporter says.
>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Either trim quoted text or STOP BOTTOM POSTING
2017-08-25 0:37 ` Either trim quoted text or STOP BOTTOM POSTING (was: alias appears to not work...) L A Walsh
@ 2017-08-25 14:25 ` cyg Simple
2017-08-25 16:43 ` Dan Kegel
2017-08-26 6:04 ` convenient trimming of quoted text to make points L A Walsh
0 siblings, 2 replies; 24+ messages in thread
From: cyg Simple @ 2017-08-25 14:25 UTC (permalink / raw)
To: cygwin
On 8/24/2017 8:36 PM, L A Walsh wrote:
> If you can't trim your quoted text, then please stop burying the
> new stuff on the bottom.
>
Did you wake up on the wrong side of the bed. I see from a google
search that you've had problems with style in the past even on this list.
>
> I've noticed it is most often bottom-poster who include all
> previous quotes -- and that's the worst -- having to WADE
> through EVERYTHING that came before, when EVERYONE on the
> list has already received it. That's the rub: if you
List etiquette frowns on both bottom and top posting and warrants to
interleaving the replies.
> want to bottom-post, then trim what you are quoting to that
> which is necessary (and that's fine w/me).
> But if you are not good about trimming, then put the *IMPORTANT*
> stuff first (your NEW text). That's write -- the most important
s/write/right
> thing in your email is what YOU are writing. It should come
> first. If you feel a need to quote large parts of the previous
> conversation, put it in an appendix -- because most people will
> have already received and read it. Including it again is
> "superfluous", but that's why there are appendices.
What I'm replying to follows what I'm quoting to give context to the
reply. My reply should never be more important that the reason for the
response. Without the context of what I'm responding to there is no
reason to reply but I should create a new subject and thread.
>
> I DO pay attention to the subject BTW.
Well all and good but you hijacked a thread to bring home a point which
is in itself just wrong.
https://wiki.openstack.org/wiki/MailingListEtiquette
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Either trim quoted text or STOP BOTTOM POSTING
2017-08-25 14:25 ` Either trim quoted text or STOP BOTTOM POSTING cyg Simple
@ 2017-08-25 16:43 ` Dan Kegel
2017-08-26 6:04 ` convenient trimming of quoted text to make points L A Walsh
1 sibling, 0 replies; 24+ messages in thread
From: Dan Kegel @ 2017-08-25 16:43 UTC (permalink / raw)
To: cygwin
I hadn't heard the name 'interleaved' style, I think that used to be
called top-posting plus appropriate trimming.
I sympathize with folks who are frustrated with whippersnappers not
knowing email conventions.
(It's almost as bad as not knowing how to use a manual gearshift :-)
- Dan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: convenient trimming of quoted text to make points
2017-08-25 14:25 ` Either trim quoted text or STOP BOTTOM POSTING cyg Simple
2017-08-25 16:43 ` Dan Kegel
@ 2017-08-26 6:04 ` L A Walsh
2017-08-26 15:26 ` cyg Simple
1 sibling, 1 reply; 24+ messages in thread
From: L A Walsh @ 2017-08-26 6:04 UTC (permalink / raw)
To: cygwin
cyg Simple wrote:
> On 8/24/2017 8:36 PM, L A Walsh wrote:
>
>> If you can't trim your quoted text, then please stop burying the
>> new stuff on the bottom.
>>
>
> Did you wake up on the wrong side of the bed. I see from a google
> search that you've had problems with style in the past even on this list.
>
Maybe I'm one of the few who has RSI and gets irritated by having
to go through extra steps to skip large walls of text.
> List etiquette frowns on both bottom and top posting and warrants to
> interleaving the replies.
>
---
I know of no list where that is commonly practiced.
> Well all and good but you hijacked a thread to bring home a point which
> is in itself just wrong.
>
To selectively quote things in your reply to make your point is the
problem here, since I replied to the original subject, extensively.
It was you who deleted the "on-topic" part of the message to make
your point.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: convenient trimming of quoted text to make points
2017-08-26 6:04 ` convenient trimming of quoted text to make points L A Walsh
@ 2017-08-26 15:26 ` cyg Simple
2017-09-01 4:54 ` Duncan Roe
0 siblings, 1 reply; 24+ messages in thread
From: cyg Simple @ 2017-08-26 15:26 UTC (permalink / raw)
To: cygwin
On 8/26/2017 2:04 AM, L A Walsh wrote:
> cyg Simple wrote:
>> On 8/24/2017 8:36 PM, L A Walsh wrote:
>> Â
>>> If you can't trim your quoted text, then please stop burying the
>>> new stuff on the bottom.
>>> Â Â Â
>>
>> Did you wake up on the wrong side of the bed. I see from a google
>> search that you've had problems with style in the past even on this list.
>> Â
> Maybe I'm one of the few who has RSI and gets irritated by having
> to go through extra steps to skip large walls of text.
I don't know what RSI is. I might guess it to be Residual Self Image or
Remotely Sensed Imagery. ;p
>> List etiquette frowns on both bottom and top posting and warrants to
>> interleaving the replies.
>> Â
> ---
> Â Â I know of no list where that is commonly practiced.
Every list including this one since before you began using email lists.
Interleaving began back in the days before the RFC for email standards
was created. The fact that people misuse quoting doesn't change the
etiquette for using interleaving which most open source lists state to use.
>> Well all and good but you hijacked a thread to bring home a point which
>> is in itself just wrong.
>> Â
> To selectively quote things in your reply to make your point is the
> problem here, since I replied to the original subject, extensively.
> It was you who deleted the "on-topic" part of the message to make
> your point.
>
No, you changed it, the client I use elided the (was: ...) portion since
it was no longer the subject to which I was responding. And my context
to you did not include any of the original message.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: convenient trimming of quoted text to make points
2017-08-26 15:26 ` cyg Simple
@ 2017-09-01 4:54 ` Duncan Roe
2017-09-01 7:37 ` Csaba Raduly
0 siblings, 1 reply; 24+ messages in thread
From: Duncan Roe @ 2017-09-01 4:54 UTC (permalink / raw)
To: cygwin
On Sat, Aug 26, 2017 at 11:26:10AM -0400, cyg Simple wrote:
> On 8/26/2017 2:04 AM, L A Walsh wrote:
> > cyg Simple wrote:
> >> On 8/24/2017 8:36 PM, L A Walsh wrote:
> >> Â
> >>> If you can't trim your quoted text, then please stop burying the
> >>> new stuff on the bottom.
> >>> Â Â Â
> >>
> >> Did you wake up on the wrong side of the bed. I see from a google
> >> search that you've had problems with style in the past even on this list.
> >> Â
> > Maybe I'm one of the few who has RSI and gets irritated by having
> > to go through extra steps to skip large walls of text.
>
> I don't know what RSI is. I might guess it to be Residual Self Image or
> Remotely Sensed Imagery. ;p
RSI == Repetitive Strain Injury. It's a real medical condition.
>
> >> List etiquette frowns on both bottom and top posting and warrants to
> >> interleaving the replies.
> >> Â
> > ---
> > Â Â I know of no list where that is commonly practiced.
>
> Every list including this one since before you began using email lists.
> Interleaving began back in the days before the RFC for email standards
> was created. The fact that people misuse quoting doesn't change the
> etiquette for using interleaving which most open source lists state to use.
>
> >> Well all and good but you hijacked a thread to bring home a point which
> >> is in itself just wrong.
> >> Â
> > To selectively quote things in your reply to make your point is the
> > problem here, since I replied to the original subject, extensively.
> > It was you who deleted the "on-topic" part of the message to make
> > your point.
> >
>
> No, you changed it, the client I use elided the (was: ...) portion since
> it was no longer the subject to which I was responding. And my context
> to you did not include any of the original message.
>
> --
> cyg Simple
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: convenient trimming of quoted text to make points
2017-09-01 4:54 ` Duncan Roe
@ 2017-09-01 7:37 ` Csaba Raduly
2017-09-01 12:38 ` cyg Simple
0 siblings, 1 reply; 24+ messages in thread
From: Csaba Raduly @ 2017-09-01 7:37 UTC (permalink / raw)
To: cygwin list
On Fri, Sep 1, 2017 at 6:54 AM, Duncan Roe wrote:
> On Sat, Aug 26, 2017 at 11:26:10AM -0400, cyg Simple wrote:
(snip)
>> I don't know what RSI is. I might guess it to be Residual Self Image or
>> Remotely Sensed Imagery. ;p
>
> RSI == Repetitive Strain Injury. It's a real medical condition.
It's the pain you get in your fingers from having to scroll past
fifty-five lines of quoted text, when somebody responded to one line
and forgot to delete the irrelevant fifty-four.
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: convenient trimming of quoted text to make points
2017-09-01 7:37 ` Csaba Raduly
@ 2017-09-01 12:38 ` cyg Simple
0 siblings, 0 replies; 24+ messages in thread
From: cyg Simple @ 2017-09-01 12:38 UTC (permalink / raw)
To: cygwin
On 9/1/2017 3:37 AM, Csaba Raduly wrote:
> On Fri, Sep 1, 2017 at 6:54 AM, Duncan Roe wrote:
>> On Sat, Aug 26, 2017 at 11:26:10AM -0400, cyg Simple wrote:
> (snip)
>>> I don't know what RSI is. I might guess it to be Residual Self Image or
>>> Remotely Sensed Imagery. ;p
>>
>> RSI == Repetitive Strain Injury. It's a real medical condition.
I don't doubt a medical condition but throwing out acronyms without some
pointer for those who don't know what the reference is leads to someone
getting the wrong context. Maybe this one should be a candidate for the
Cygwin acronym list.
>
> It's the pain you get in your fingers from having to scroll past
> fifty-five lines of quoted text, when somebody responded to one line
> and forgot to delete the irrelevant fifty-four.
My email client folds the excessive quoted lines and only if I don't
know the context do I need to open the folds. Maybe someone with RSI
should consider updating their client. Complaining never got much done
and this bike shed topic has been discussed many times with little
noticed effect.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
2017-08-22 19:47 Kaz Kylheku
@ 2017-08-25 2:23 ` L A Walsh
0 siblings, 0 replies; 24+ messages in thread
From: L A Walsh @ 2017-08-25 2:23 UTC (permalink / raw)
To: cygwin
Kaz Kylheku wrote:
>
> There is an issue there (though not for the Cygwin project).
>
> I don't see where ...
> "expanding aliases in interactive mode, but ignoring them in
> non-interactive
> operation" [is required by POSIX].
>
> POSIX seems to unequivocally be calling for Alias Expansion to occur
> under all conditions.
Could you list the http reference for that?
>
> And, indeed, this is not a bug in Bash; they know that this is
> a POSIX deviation. Because, voila, aliases *are* expanded in
> script mode if we do one of two things:
>
> #!/bin/bash --posix
>
> #!/bin/sh
----
Only in cygwin (4.4.12).
In my linux version of bash, expand_aliases is not turned on
in POSIX mode. Created scripts:
#!/bin/sh
shopt -s |grep expand
and
#!/bin/bash --posix
shopt -s |grep expand
On cygwin they show:
expand_aliases on
Not so on linux (same version of bash 4.4.12)
Hmmm...
Is there a definitive reference for this feature?
Thanks!
-l
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: alias appears to not work inside a called bash script
@ 2017-08-22 19:47 Kaz Kylheku
2017-08-25 2:23 ` L A Walsh
0 siblings, 1 reply; 24+ messages in thread
From: Kaz Kylheku @ 2017-08-22 19:47 UTC (permalink / raw)
To: cygwin
On 21.08.2017 15:53, Eliot Moss wrote:
> From the bash man page:
>
> "Aliases are ot expanded when the shell is not interactive, unless
> the expand_aliases shell option
> is set using shopt (see the description of shopt under SHELL BUILTIN
> COMMANDS below)."
>
> Could that be the root of your difficulty?
There is an issue there (though not for the Cygwin project).
I don't see where this behavior is required in POSIX: that is,
expanding aliases in interactive mode, but ignoring them in
non-interactive
operation.
POSIX seems to unequivocally be calling for Alias Expansion to occur
under all conditions.
And, indeed, this is not a bug in Bash; they know that this is
a POSIX deviation. Because, voila, aliases *are* expanded in
script mode if we do one of two things:
#!/bin/bash --posix
#!/bin/sh
Bash in POSIX mode knows every well that it had better
expand aliases regardless of non-interactive operation.
However, *suppressing* a useful behavior in a default, non-standard
mode is highly counter-intuitive.
I mean we can't even call this a vendor *extension* with a straight
face. What do we call this? "retraction?" :)
"To disable the vendor-specific retraction that aliases don't
work, operate bash in POSIX mode, or use the expand_aliases
shopt."
:)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2017-09-01 12:38 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-08-21 22:30 alias appears to not work inside a called bash script Michel LaBarre
2017-08-21 22:53 ` Eliot Moss
2017-08-21 22:55 ` alias appears to not work inside a called bash scripty Duncan Roe
2017-08-22 1:01 ` Michel LaBarre
2017-08-22 14:31 ` alias appears to not work inside a called bash script Stephen John Smoogen
2017-08-22 14:47 ` Eliot Moss
2017-08-22 15:19 ` Stephen John Smoogen
2017-08-22 16:46 ` Eliot Moss
2017-08-22 18:25 ` Stephen John Smoogen
2017-08-25 0:37 ` Either trim quoted text or STOP BOTTOM POSTING (was: alias appears to not work...) L A Walsh
2017-08-25 14:25 ` Either trim quoted text or STOP BOTTOM POSTING cyg Simple
2017-08-25 16:43 ` Dan Kegel
2017-08-26 6:04 ` convenient trimming of quoted text to make points L A Walsh
2017-08-26 15:26 ` cyg Simple
2017-09-01 4:54 ` Duncan Roe
2017-09-01 7:37 ` Csaba Raduly
2017-09-01 12:38 ` cyg Simple
2017-08-22 17:08 ` alias appears to not work inside a called bash script cyg Simple
2017-08-22 17:14 ` Eliot Moss
2017-08-22 19:07 ` cyg Simple
2017-08-22 19:11 ` cyg Simple
2017-08-23 19:08 ` Eric Blake
2017-08-22 19:47 Kaz Kylheku
2017-08-25 2:23 ` L A Walsh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).