Re: [ITA] w32api-3.0b_svn5368-1
On 8/22/2012 06:26, JonY wrote: According to mingw.org basetyps.h, GUID_SECT was only necessary for ancient GCC versions. At a minimum, we should be able to just remove the GUID_SECT from those defines. Unfortunately just ifndef _W64 those defines entirely leads to link errors: hw/xwin/winengine.c:107: undefined reference to `_IID_IDirectDraw4' winshaddd.o: In function `winAllocateFBShadowDD': hw/xwin/winshaddd.c:253: undefined reference to `_IID_IDirectDraw2' winshadddnl.o: In function `winAllocateFBShadowDDNL': hw/xwin/winshadddnl.c:285: undefined reference to `_IID_IDirectDraw4' winpfbdd.o: In function `winAllocateFBPrimaryDD': hw/xwin/winpfbdd.c:89: undefined reference to `_IID_IDirectDraw2' mingw-w64 ddraw.h already has them, though they're inlined, gcc doesn't like inlined data. DEFINE_GUID may need fixing, or at least instanced in libuuid or libddraw. I'll need to talk to to the Jacek from Wine to get a solution. Here's a quick and dirty workaround, add and compile the following file and link it with the failing executable: = #define INITGUID 1 #include ddraw.h = signature.asc Description: OpenPGP digital signature
Re: HEADSUP: ruby-1.9.3 (attn: Jari, David, Ken)
On 8/21/2012 7:53 PM, Yaakov (Cygwin/X) wrote:
On 2012-08-21 04:38, Yaakov (Cygwin/X) wrote:
Upstream has announced EOL for Ruby 1.8.x; right now it is receiving
only security fixes. Therefore, it is now time to move on to the
now-stable 1.9.x series.
For the moment, the latest release is here:
ftp://ftp.cygwinports.org/pub/cygwinports/uploads/ruby/
I have moved 1.9.3-p194-1 into the distro as a test release. Please
update and/or test your packages ASAP.
I tested three of the TeX Live scripts (match_parens, epspdf, and
texexec), and all fail with a slew of error messages. As an example,
I'm attaching the output of 'texexec test.tex 2 texexec.out'. I'm also
attaching test.tex; it's a ConTeXt file that I successfully compiled
with texexec two days ago.
I don't know anything about ruby, but the error messages don't appear to
me to have anything to do with the specific scripts.
Ken
\starttext
\startstandardmakeup
\midaligned{How to make a document.}
\midaligned{by}
\midaligned{The Author}
\stopstandardmakeup
\completecontent
\chapter{Introduction}
... your text\index{indexentry} ...
\chapter{One Chapter}
\section[firstsection]{The first section}
... your text ...
\section{The second section}
\subsection{the first sub section}
... your text\index{another indexentry} ...
\subsection{the second sub section}
... your text ...
\section{The third section}
... your text ...
\chapter{Another Chapter}
... your text ...
\chapter[lastchapter]{The Last Chapter}
... your text ...
\completeindex
\stoptext
/usr/lib/ruby/1.9.1/rubygems.rb:31:in `require':
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:136: syntax error, unexpected
tCONSTANT, expecting keyword_end (SyntaxError)
CONFIG[CXX] = g++
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:136: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[CXX] = g++
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:137: syntax error, unexpected
tCONSTANT, expecting keyword_end
CONFIG[OBJEXT] = o
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:137: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[OBJEXT] = o
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:138: syntax error, unexpected
tCONSTANT, expecting keyword_end
CONFIG[CPPFLAGS] = $(DEFS) $(cppflags)
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:138: syntax error, unexpected
$undefined, expecting keyword_end
CONFIG[CPPFLAGS] = $(DEFS) $(cppflags)
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:139: syntax error, unexpected
tCONSTANT, expecting keyword_end
CONFIG[LDFLAGS] = -L.
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:139: syntax error, unexpected
tSTRING_BEG
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:140: syntax error, unexpected
tCONSTANT, expecting keyword_end
CONFIG[CFLAGS] = -ggdb -O2 -pipe -fno-strict-aliasing
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:140: syntax error, unexpected
tUMINUS, expecting keyword_do or '{' or '('
CONFIG[CFLAGS] = -ggdb -O2 -pipe -fno-strict-aliasing
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:140: syntax error, unexpected
tSTRING_BEG, expecting keyword_do or '{' or '('
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:141: syntax error, unexpected
tCONSTANT, expecting keyword_end
CONFIG[CC] = gcc
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:141: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[CC] = gcc
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:142: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target_os] = cygwin
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:142: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target_os] = cygwin
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:143: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target_vendor] = pc
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:143: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target_vendor] = pc
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:144: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target_cpu] = i386
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:144: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target_cpu] = i386
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:145: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target] = i386-pc-cygwin
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:145: syntax error, unexpected
tIDENTIFIER, expecting keyword_end
CONFIG[target] = i386-pc-cygwin
^
/usr/lib/ruby/1.9.1/i386-cygwin/rbconfig.rb:145: syntax error, unexpected
Re: HEADSUP: ruby-1.9.3 (attn: Jari, David, Ken)
On 8/22/2012 6:48 AM, Ken Brown wrote: On 8/21/2012 7:53 PM, Yaakov (Cygwin/X) wrote: On 2012-08-21 04:38, Yaakov (Cygwin/X) wrote: Upstream has announced EOL for Ruby 1.8.x; right now it is receiving only security fixes. Therefore, it is now time to move on to the now-stable 1.9.x series. For the moment, the latest release is here: ftp://ftp.cygwinports.org/pub/cygwinports/uploads/ruby/ I have moved 1.9.3-p194-1 into the distro as a test release. Please update and/or test your packages ASAP. I tested three of the TeX Live scripts (match_parens, epspdf, and texexec), and all fail with a slew of error messages. As an example, I'm attaching the output of 'texexec test.tex 2 texexec.out'. I'm also attaching test.tex; it's a ConTeXt file that I successfully compiled with texexec two days ago. I don't know anything about ruby, but the error messages don't appear to me to have anything to do with the specific scripts. I'm getting the same errors from the subversion configure script's checking rb_hash_foreach test. -- David Rothenberger daver...@acm.org Morton's Law: If rats are experimented upon, they will develop cancer.
Re: HEADSUP: ruby-1.9.3 (attn: Jari, David, Ken)
On 2012-08-22 08:48, Ken Brown wrote: On 8/21/2012 7:53 PM, Yaakov (Cygwin/X) wrote: I have moved 1.9.3-p194-1 into the distro as a test release. Please update and/or test your packages ASAP. I tested three of the TeX Live scripts (match_parens, epspdf, and texexec), and all fail with a slew of error messages. As an example, I'm attaching the output of 'texexec test.tex 2 texexec.out'. I'm also attaching test.tex; it's a ConTeXt file that I successfully compiled with texexec two days ago. I don't know anything about ruby, but the error messages don't appear to me to have anything to do with the specific scripts. No, that's a problem with the revision I uploaded. Sorry about that. Please try again with 1.9.3-p194-2. Yaakov
Re: [RFU] promote texlive-collection-basic-20120628-2 from test to current
On 2012-08-21 06:21, Ken Brown wrote:
D=http://sanibeltranquility.com/cygwin/release/TeX
TC=texlive-collection
wget -x -nH --cut-dirs=2 ${D}/${TC}-basic/setup.hint
cd TeX
rm \
${D}/${TC}-basic/${TC}-basic-20120312-2.tar.bz2\
${D}/${TC}-basic/${TC}-basic-20120312-2-src.tar.bz2
Done and done (without the latter ${D}'s, of course :-)).
Yaakov
Re: HEADSUP: ruby-1.9.3 (attn: Jari, David, Ken)
On 8/22/2012 2:36 PM, Yaakov (Cygwin/X) wrote: On 2012-08-22 08:48, Ken Brown wrote: On 8/21/2012 7:53 PM, Yaakov (Cygwin/X) wrote: I have moved 1.9.3-p194-1 into the distro as a test release. Please update and/or test your packages ASAP. I tested three of the TeX Live scripts (match_parens, epspdf, and texexec), and all fail with a slew of error messages. As an example, I'm attaching the output of 'texexec test.tex 2 texexec.out'. I'm also attaching test.tex; it's a ConTeXt file that I successfully compiled with texexec two days ago. I don't know anything about ruby, but the error messages don't appear to me to have anything to do with the specific scripts. No, that's a problem with the revision I uploaded. Sorry about that. Please try again with 1.9.3-p194-2. The three scripts I tried before now seem to work fine. I'll do some further testing as I have time, but it looks good so far. Ken
Re: [RFU] mingw64 headers and runtime refresh
On 8/19/2012 21:53, JonY wrote: Hi, New uploads at: http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-i686-runtime/mingw64-i686-runtime-3.0b_svn5373-1-src.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-i686-runtime/mingw64-i686-runtime-3.0b_svn5373-1.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-i686-runtime/setup.hint http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-i686-headers/mingw64-i686-headers-3.0b_svn5373-1-src.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-i686-headers/mingw64-i686-headers-3.0b_svn5373-1.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-i686-headers/setup.hint http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-x86_64-headers/mingw64-x86_64-headers-3.0b_svn5373-1-src.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-x86_64-headers/mingw64-x86_64-headers-3.0b_svn5373-1.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-x86_64-headers/setup.hint http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-x86_64-runtime/mingw64-x86_64-runtime-3.0b_svn5373-1-src.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-x86_64-runtime/mingw64-x86_64-runtime-3.0b_svn5373-1.tar.bz2 http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/mingw64-x86_64-runtime/setup.hint Please remove 4694: find mingw64-*/ -name '*svn4694-1*' -type f | xargs rm Thanks. Ping. signature.asc Description: OpenPGP digital signature
Re: HEADSUP: ruby-1.9.3 (attn: Jari, David, Ken)
On 8/21/2012 2:38 AM, Yaakov (Cygwin/X) wrote: Upstream has announced EOL for Ruby 1.8.x; right now it is receiving only security fixes. Therefore, it is now time to move on to the now-stable 1.9.x series. The following distro packages depend on Ruby, by maintainer: David Rothenberger: subversion-ruby (patch for 1.9 here[1]) Thanks for the patch. I've built a test release of subversion against ruby 1.9. All the ruby tests pass except for one, but there's a FIXME comment in the test so I think that's okay. I don't use the Ruby bindings myself so that's about as much as I can do. I'm not sure if an official RFU is appropriate (since the test Ruby release was never announced), but here are the files in case someone's interested: wget -x -nH --cut-dirs=2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-1.7.6-2-src.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-apache2/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-apache2/subversion-apache2-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-debuginfo/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-debuginfo/subversion-debuginfo-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-devel/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-devel/subversion-devel-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-gnome/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-gnome/subversion-gnome-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-perl/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-perl/subversion-perl-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-python/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-python/subversion-python-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-ruby/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-ruby/subversion-ruby-1.7.6-2.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-tools/setup.hint \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-tools/subversion-tools-1.7.6-2.tar.bz2 -- David Rothenberger daver...@acm.org Successful and fortunate crime is called virtue. -- Seneca
Re: Gode tekster selger best -- Spam
On Wed, Aug 22, 2012 at 06:52:50AM +0200, Herbert Stocker wrote: To the list: i checked with Google Translate, this is spam. Iaw, an advertising for an off-topic web site. Yes, it's pretty obvious that this is spam without a translation. These kind of things get blocked when they show up. There is no need for you to do anything and, in fact, responding to spam and quoting the article is a good way to get added as a spammer yourself. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Oddity with cygport, debuginfo generation, and rxvt-unicode
On Tue, Aug 21, 2012 at 11:40 PM, Charles Wilson wrote: Oh, let me think...never. I'm still (re)training people that spaces are evil. Don't even get me started on hashes and shell metas in filenames... Oh, just rename them to be asc(0x010); that's always good for a laugh. ;) -- Earnie -- https://sites.google.com/site/earnieboyd -- 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
Re: TexLive's ConTeXt runtime error..
I reinstalled all cygwin zlib modules and the problem persisted. The only zlib I found was the cygwin installed one. Since it is POSIX compliant and TeXLive installs with it it shouldn't be a problem, I should think. But, there is one due to, pdftex I think. Regards On Mon, Aug 20, 2012 at 11:24 PM, Achim Gratz strom...@nexgo.de wrote: Wynfield Henman wynfield at gmail.com writes: This results in: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.5, library: 1.2.7) Reinstall zlib and install zlib-devel. If that doesn't help, check where the zlib.h header file is found (it shouldn't be from a Cygwin package in that case). Regards, Achim. -- 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
Re: /etc/profile
On Tue, Aug 21, 2012 at 10:16:28AM +, Achim Gratz wrote: I'm removing the Windows PATH in my startup scripts since there's nothing in there that I think should be accessible from Cygwin. For (t)csh this is easy enough to do with dropping a script into /etc/profile.d that gets executed first, but there's no such provision for sh and the ilk since PATH is set up already before it get there. Now, unless profile gets changed I can still cut off /usr/local/bin:/usr/bin: with a profile.d script, but I think it might be preferrable that the Windows path gets recorded into ORIGINAL_PATH or some similar name at the beginning of profile. It would then be a simple matter to later add the Windows path where appropriate, but I don't think the default path should have it at all. Also, there are two things in profile that may admit slight improvement (a place where LC_COLLATE is specified just for one command and better guarding against a missing or non-cdable /etc/skel). All three changes will be available in the next release (profile_d modification taken from your last version in this thread). Thanks. -- Primary key fingerprint: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56 signature.asc Description: Digital signature
Re: /etc/profile
David Sastre Medina writes: All three changes will be available in the next release (profile_d modification taken from your last version in this thread). Thanks. Thank you. If you'd rather have a complete patch, let me know and I'll post it or send it to you via email, as you prefer. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- 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
Re: TexLive's ConTeXt runtime error..
On 8/22/2012 2:06 PM, Wynfield Henman wrote: Ken, thanks for replying and helping. Here is the information that you asked about. The example ConTeXt file, example.tex, is attached hereto. PATH is in the cygcheck.out file. No other zlib.h was found. I can't reproduce the problem on my system, using either the native TeX Live or Cygwin's TeX Live. Try putting /usr/local/texlive/2012/bin/i386-cygwin first in your path instead of last. (That's what I do when I want to test something using native TeX Live.) Ken -- 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
Re: /etc/profile
On Wed, Aug 22, 2012 at 09:15:58PM +0200, Achim Gratz wrote: If you'd rather have a complete patch, let me know and I'll post it or send it to you via email, as you prefer. I'm having this on github now for easier handling. Check https://github.com/dsastrem/base-files.git -- Primary key fingerprint: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56 signature.asc Description: Digital signature
Re: TexLive's ConTeXt runtime error..
Wynfield Henman writes: I reinstalled all cygwin zlib modules and the problem persisted. The only zlib I found was the cygwin installed one. Since it is POSIX compliant and TeXLive installs with it it shouldn't be a problem, I should think. But, there is one due to, pdftex I think. The file to look for is the zlib.h header file. This results in: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.5, library: 1.2.7) The Lua component of ConTeX has been compiled with a 1.2.5 header file. If you didn't have that version installed at the time you compiled TeXlive, then there must be another zlib.h, probably delivered with TeXlive. You need to configure the build to use Cygwins zlib.h instead. Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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
Re: /etc/profile
On 8/22/12 12:10 PM, David Sastre Medina wrote: On Tue, Aug 21, 2012 at 10:16:28AM +, Achim Gratz wrote: I'm removing the Windows PATH in my startup scripts since there's nothing in there that I think should be accessible from Cygwin. For (t)csh this is easy enough to do with dropping a script into /etc/profile.d that gets executed first, but there's no such provision for sh and the ilk since PATH is set up already before it get there. Now, unless profile gets changed I can still cut off /usr/local/bin:/usr/bin: with a profile.d script, but I think it might be preferrable that the Windows path gets recorded into ORIGINAL_PATH or some similar name at the beginning of profile. It would then be a simple matter to later add the Windows path where appropriate, but I don't think the default path should have it at all. Also, there are two things in profile that may admit slight improvement (a place where LC_COLLATE is specified just for one command and better guarding against a missing or non-cdable /etc/skel). All three changes will be available in the next release (profile_d modification taken from your last version in this thread). Are you sure that's actually a good idea? I don't agree with this logic: I'm removing the Windows PATH in my startup scripts since there's nothing in there that I think should be accessible from Cygwin. People execute Windows programs using Cygwin all the time. With this change, basic things like cmd and notepad will fail to work. Working with Windows programs is the *point* of Cygwin. I really don't think this change should go into the default startup scripts. signature.asc Description: OpenPGP digital signature
Re: /etc/profile
David Sastre Medina writes: I'm having this on github now for easier handling. Check https://github.com/dsastrem/base-files.git Ah, nice. Everythings OK, thank you. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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
Re: /etc/profile
Daniel Colascione writes:
People execute Windows programs using Cygwin all the time. With this
change, basic things like cmd and notepad will fail to work.
Working with Windows programs is the *point* of Cygwin. I really don't
think this change should go into the default startup scripts.
The change is about giving users a choice. You can now drop a script
into profile.d that just does:
PATH=${PATH}:${ORIGINAL_PATH}
and have exactly the same behaviour as you have now (and David might
consider installing that by default). Or you don't and are not bothered
by the useless stuff corporate IT adds to Windows PATH without even
checking that it works correctly on Windows, let alone together with
Cygwin.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
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
Re: /etc/profile
On Wed, Aug 22, 2012 at 10:24:24PM +0200, Achim Gratz wrote:
Daniel Colascione writes:
People execute Windows programs using Cygwin all the time. With this
change, basic things like cmd and notepad will fail to work.
Working with Windows programs is the *point* of Cygwin. I really don't
think this change should go into the default startup scripts.
The change is about giving users a choice. You can now drop a script
into profile.d that just does:
PATH=${PATH}:${ORIGINAL_PATH}
and have exactly the same behaviour as you have now (and David might
consider installing that by default). Or you don't and are not bothered
by the useless stuff corporate IT adds to Windows PATH without even
checking that it works correctly on Windows, let alone together with
Cygwin.
If we are changing a longstanding behavior then I agree with Daniel that
this is a bad idea. You're just asking for people to be confused.
If you want to make it easy to remove the Windows PATH then I guess I
can see why that would be useful but it seems like anyone for whom this
would be an issue would know how to do this anyway so I don't see why we
have to go to great lengths to accommodate anyone who wants this.
cgf
--
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
Re: /etc/profile
Greetings, Achim Gratz!
People execute Windows programs using Cygwin all the time. With this
change, basic things like cmd and notepad will fail to work.
Working with Windows programs is the *point* of Cygwin. I really don't
think this change should go into the default startup scripts.
The change is about giving users a choice. You can now drop a script
into profile.d that just does:
PATH=${PATH}:${ORIGINAL_PATH}
The point it, I don't want this.
My $PATH is set in Windows, and I do not modify it in startup scripts.
--
WBR,
Andrey Repin (anrdae...@freemail.ru) 23.08.2012, 00:44
Sorry for my terrible english...
--
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
Re: /etc/profile
Christopher Faylor writes: If we are changing a longstanding behavior then I agree with Daniel that this is a bad idea. You're just asking for people to be confused. Again, I'm not arguing for changing the default. In fact, as long as ORIGINAL_PATH stays available it might even still be added to PATH in /etc/profile, although I still think it is cleaner to install /etc/profile.d/00_add_windows_path.sh in base-files with the contents I've shown. If it's already been added then removing it with just the means of a POSIX shell is a bit involved, but even that would be a possibility. If you want to make it easy to remove the Windows PATH then I guess I can see why that would be useful but it seems like anyone for whom this would be an issue would know how to do this anyway so I don't see why we have to go to great lengths to accommodate anyone who wants this. The issue is that to effect that customization I have to change a file that is not supposed to be changed (since that prevents any updates from getting to it automatically). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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
Re: /etc/profile
On Wed, Aug 22, 2012 at 01:13:37PM -0700, Daniel Colascione wrote:
On 8/22/12 12:10 PM, David Sastre Medina wrote:
On Tue, Aug 21, 2012 at 10:16:28AM +, Achim Gratz wrote:
I'm removing the Windows PATH in my startup scripts since there's nothing
in
there that I think should be accessible from Cygwin.
All three changes will be available in the next release (profile_d
modification taken from your last version in this thread).
Are you sure that's actually a good idea? I don't agree with this logic:
People execute Windows programs using Cygwin all the time. With this
change, basic things like cmd and notepad will fail to work.
Working with Windows programs is the *point* of Cygwin. I really don't
think this change should go into the default startup scripts.
I for one never start windows programs from within a shell, with the
exception of firefox, and for that I registered an entry in the
alternatives system (x-www-browser), however, I take your advice and
I'll give this a second thought, and also would like to hear from
others' opnion wrt to this.
Obviously, ORIGINAL_PATH (as proposed in Achim's patch) would
still hold the native Windows' PATH, so it'd be very easy to include a
(commented?) line using it, so it would be easy to switch it:
#PATH=/usr/local/bin:/usr/bin:${ORIGINAL_PATH}
--
Primary key fingerprint: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56
signature.asc
Description: Digital signature
Re: /etc/profile
Andrey Repin writes:
Greetings, Achim Gratz!
People execute Windows programs using Cygwin all the time. With this
change, basic things like cmd and notepad will fail to work.
Working with Windows programs is the *point* of Cygwin. I really don't
think this change should go into the default startup scripts.
The change is about giving users a choice. You can now drop a script
into profile.d that just does:
PATH=${PATH}:${ORIGINAL_PATH}
The point it, I don't want this.
You do realise that this is exactly what is done today, just at a
different place, do you?
My $PATH is set in Windows, and I do not modify it in startup scripts.
Yes you do, in /etc/profile - check it yourself.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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
Re: /etc/profile
On Wed, Aug 22, 2012 at 10:55:08PM +0200, David Sastre Medina wrote:
On Wed, Aug 22, 2012 at 01:13:37PM -0700, Daniel Colascione wrote:
On 8/22/12 12:10 PM, David Sastre Medina wrote:
On Tue, Aug 21, 2012 at 10:16:28AM +, Achim Gratz wrote:
I'm removing the Windows PATH in my startup scripts since there's nothing
in
there that I think should be accessible from Cygwin.
All three changes will be available in the next release (profile_d
modification taken from your last version in this thread).
Are you sure that's actually a good idea? I don't agree with this logic:
People execute Windows programs using Cygwin all the time. With this
change, basic things like cmd and notepad will fail to work.
Working with Windows programs is the *point* of Cygwin. I really don't
think this change should go into the default startup scripts.
I for one never start windows programs from within a shell, with the
exception of firefox, and for that I registered an entry in the
alternatives system (x-www-browser), however, I take your advice and
I'll give this a second thought, and also would like to hear from
others' opnion wrt to this.
Obviously, ORIGINAL_PATH (as proposed in Achim's patch) would
still hold the native Windows' PATH, so it'd be very easy to include a
(commented?) line using it, so it would be easy to switch it:
#PATH=/usr/local/bin:/usr/bin:${ORIGINAL_PATH}
I'll just reiterate what Daniel said again: We can't make things like
cmd or notepad stop working. That would be a disaster.
I wasn't really following the discussion, and don't really want to check
stuff out in git to see what's going on, but if the proposed change just
makes it possible for purists to remove the Windows PATH from the Cygwin
one however that's great. Otherwise, removing the Windows path entirely
really won't please very many people.
cgf
--
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
Re: /etc/profile
On Wed, Aug 22, 2012 at 05:18:31PM -0400, Christopher Faylor wrote: I'll just reiterate what Daniel said again: We can't make things like cmd or notepad stop working. That would be a disaster. I wasn't really following the discussion, and don't really want to check stuff out in git to see what's going on, but if the proposed change just makes it possible for purists to remove the Windows PATH from the Cygwin one however that's great. Otherwise, removing the Windows path entirely really won't please very many people. ACK. I'll keep PATH untouched and see if there are other ways to offer this functionality as an option. -- Primary key fingerprint: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56 signature.asc Description: Digital signature
Re: /etc/profile
On 8/22/2012 1:50 PM, Achim Gratz wrote: The issue is that to effect that customization I have to change a file that is not supposed to be changed (since that prevents any updates from getting to it automatically). I've long since (circa 1994 or so) had a script called set_path that I can source to set my path from scratch. My ~/.bashrc calls it. I can add on different directories as required from my various clients. Directories only get added to the path if they exist. Now why can't you do similar? It would not be changing a file that is not supposed to be changes rather it would be changing files that you own and that should be changed. It's your environment - take control of it! -- Andrew DeFaria http://defaria.com Artificial Intelligence usually beats real stupidity. -- 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
Re: /etc/profile
Christopher Faylor writes: I'll just reiterate what Daniel said again: We can't make things like cmd or notepad stop working. That would be a disaster. Yes, and nobody proposed otherwise. I wasn't really following the discussion, and don't really want to check stuff out in git to see what's going on, but if the proposed change just makes it possible for purists to remove the Windows PATH from the Cygwin one however that's great. OK, here it is again in a nutshell, it has two parts: 1. instead of adding the windows PATH in /etc/profile (which doesn't need it _at all_), just record it there into ORIGINAL_PATH. 2. Add a script to /etc/profile.d which concatenates the Cygwin and the windows path to provide the same net result as todays /etc/profile. I hope this avoids more TLDR; Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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
