Pushed as obvious.
* bootstrap (func_require_buildreq_autobuild)
(func_require_buildreq_automake): Vi's delete word command is
too greedy and also eats trailing whitespace before following
non-word-chars. Put back the spaces it ate so that
syntax-checks pass once again.
Signed-off-by: Gary V
: eliminate spaces in the library search path.
* libltdl/m4/libtool.m4 (_LT_SYS_DYNAMIC_LINKER) [mingw, cygwin]
cl*, sys_lib_search_path_spec: The LIB path variable telling
where MSVC looks for libraries is with high probably containing
directory names with spaces. Convert those directory names
Den 2010-09-21 09:37 skrev Peter Rosin:
I know it's late for the release, but I'd like to squeeze this one in
too, if at all possible. After all, it doesn't affect anything but MSVC.
With the patch, I get
sys_lib_search_path_spec=/c/PROGRA~1/MID05A~1/VC/ATLMFC/LIB
? Is this an API you just made up? If not, where is it
documented? Hmm, we used it before, so I guess that's not new.
Subject: [PATCH] msvc: eliminate spaces in the library search path.
* libltdl/m4/libtool.m4 (_LT_SYS_DYNAMIC_LINKER) [mingw, cygwin]
cl*, sys_lib_search_path_spec: The LIB path
it, without improvements/additions to MSYS.
+ ;;
+cygwin*)
+ # Convert to unix form, then to dos form, then back to unix form
+ # but this time dos style (no spaces!) so that the unix form looks
+ # like /cygdrive/c/PROGRA~1:/cygdr...
+ sys_lib_search_path_spec=`cygpath
: eliminate spaces in the library search path.
* libltdl/m4/libtool.m4 (_LT_SYS_DYNAMIC_LINKER) [mingw, cygwin]
cl*, sys_lib_search_path_spec: The LIB path variable telling
where MSVC looks for libraries is with high probably containing
s/probably/probability/ ? If yes, I'd rather write is likely
Den 2010-09-21 20:08 skrev Charles Wilson:
On 9/21/2010 1:33 PM, Ralf Wildenhues wrote:
* Peter Rosin wrote on Tue, Sep 21, 2010 at 09:37:16AM CEST:
+ do
+IFS=$lt_save_ifs
+# Let DOS variable expansion print the short 8.3 style file name.
+lt_path=`cd $lt_path
...@lysator.liu.se
Date: Tue, 21 Sep 2010 20:31:37 +0200
Subject: [PATCH] msvc: eliminate spaces in the library search path.
* libltdl/m4/libtool.m4 (_LT_SYS_DYNAMIC_LINKER) [mingw, cygwin]
cl*, sys_lib_search_path_spec: The LIB path variable telling
where MSVC looks for libraries is likely to contain
Hi Gary,
will texinfo render badly spaced dvi (or other) if we use single
spaces after a period, or even if we are inconsistent throughout an
input document?
DVI isn't the problem (TeX always does the right thing). Info is the
problem. Makeinfo does cheap text refilling. So
and the @file
branch works. Fixes stresstest.at when doing a cross from Cygwin
Two spaces after period.
Only for texinfo markup I believe, since two spaces after a period are widely
regarded as typographically bad (see the following and the reports it cites at
the end):
http://webword.com/reports
the @file branch *if* the file
names needs to be converted for the toolchain and the @file
branch works. Fixes stresstest.at when doing a cross from Cygwin
Two spaces after period.
Only for texinfo markup I believe, since two spaces after a period are
widely regarded as typographically bad (see
modern typographical conventions and insist on double spaces?
I always thought it was (fundamentally) about Emacs as well. That's
what rms told me in 1985, anyway :). At any rate, the convention ever
since GNU started was to have two spaces at the end of sentences. I
never liked two spaces in my
especially opposed to double spacing, – I'd just like to
not have to be religious about requiring it unless single spaces cause
an actual problem – but if @frenchspacing is orthogonal to the use of
single spaces after a period in texinfo documents, will texinfo render
badly spaced dvi (or other
Le 19 janv. 09 à 23:38, Ralf Wildenhues a écrit :
Bonjour Ralf!
It is true that I have been disturbed and even annoyed by tab vs.
space in some patches that gave the impression of improper
indentation.
Therefore, for a year or so, I am now using spaces only.
But it is not sufficient
Den 2009-01-21 23:13, skrev Ralf Wildenhues:
* Charles Wilson wrote on Tue, Jan 20, 2009 at 07:29:52PM CET:
Bob Friesenhahn wrote:
For many years I have had my editor configured to always use
spaces. This ensures WYSIWYG for everyone involved.
Agree 100%. I try to manually match whatever sp
On Thu, 22 Jan 2009, Peter Rosin wrote:
Den 2009-01-21 23:13, skrev Ralf Wildenhues:
* Charles Wilson wrote on Tue, Jan 20, 2009 at 07:29:52PM CET:
Bob Friesenhahn wrote:
For many years I have had my editor configured to always use
spaces. This ensures WYSIWYG for everyone involved
if it really was 24.
I find python code really annoying because it is spaces only.
Almost anyone will prefer tabs if they are the only ones working on
the source code. The problems occur when several/many people are
working on shared source code using a variety of editors.
Can we agree
* Charles Wilson wrote on Tue, Jan 20, 2009 at 07:29:52PM CET:
Bob Friesenhahn wrote:
For many years I have had my editor configured to always use
spaces. This ensures WYSIWYG for everyone involved.
Agree 100%. I try to manually match whatever sp/tab convention is in
place -- using vi
Ralf Wildenhues wrote:
OK so it seems there are more voices for spaces.
Can we agree to make the switch only after 2.2.8 though,
I would like to avoid unnecessary churn ATM.
Works for me.
--
Chuck
Bob Friesenhahn wrote:
For many years I have had my editor configured to always use
spaces. This ensures WYSIWYG for everyone involved.
Agree 100%. I try to manually match whatever sp/tab convention is in
place -- using vi if I have to -- but much prefer all spaces.
--
Chuck
differences to
creep into my new code.
This implies that there is a single, well-defined ideal state. Your
editor does not collapse 8 spaces to a TAB, mine (and some others)
does.
This causes whitespace-only changes. Very very minor, I agree, but
still a small irritation when reviewing.
I
, for a year or so, I am now using spaces only.
It is not necessary to use hard tabs. They are a form of text
compression which originated with anchient character terminals and
typewriters. Since many/most people have a habit of changing the
meaning of TAB to something other than the standard
Ralf Wildenhues wrote:
Your patch seems fine. It's so simple I have applied it to HEAD,
branch-2-0 and branch-1-5 right away. Thanks!
Thanks!
That's fine. THANKS lists your paperwork exchange. Hmm, maybe we need
to adjust that heading
| * The following people have made sufficiently
Hi Derek,
* Derek Price wrote on Thu, Jun 30, 2005 at 06:29:24PM CEST:
There is a bug which causes libtool to exit during compilation with an
error like, Can't find library `' when there are spaces in PWD. I
*snip*
Anyhow, I later created a new bash shell and accidentally used the path
24 matches
Mail list logo
