On Tue, 12 Jun 2018 at 09:53, Sven Eden wrote:
> I have a problem with a script that wants to copy a file,
> which has a variable paths build from various variables.
>
> The first variable is a possible prefix, the second an
> absolute path. If no prefix is needed, the first consists of
> just a
On 06/12/2018 03:48 AM, Corinna Vinschen wrote:
On Jun 8 12:43, Eric Blake wrote:
On 06/08/2018 12:26 PM, Hans-Bernhard Bröker wrote:
Am 08.06.2018 um 17:16 schrieb Denis Nikiforov:
/usr/include/boost/process/detail/posix/is_running.hpp:18:1: error:
non-constant condition for static
Hello everybody,
I have a problem with a script that wants to copy a file,
which has a variable paths build from various variables.
The first variable is a possible prefix, the second an
absolute path. If no prefix is needed, the first consists of
just a slash.
What I now see is the following:
On Jun 8 12:43, Eric Blake wrote:
> On 06/08/2018 12:26 PM, Hans-Bernhard Bröker wrote:
> > Am 08.06.2018 um 17:16 schrieb Denis Nikiforov:
> > > /usr/include/boost/process/detail/posix/is_running.hpp:18:1: error:
> > > non-constant condition for static assertion
> > >
On 06/12/2018 03:53 AM, Sven Eden wrote:
Hello everybody,
I have a problem with a script that wants to copy a file,
which has a variable paths build from various variables.
The first variable is a possible prefix, the second an
absolute path. If no prefix is needed, the first consists of
Hi,
I have a 32 bit cygwin installation of 8 years of age in an amd64 PC with 2 GB
of RAM with Windows 10. So far it's been so good. I never had the need to use a
64 bit Windows, but recently 64 bit has become mainstream and I also started
having low memory issues, so I upgraded to 4 GB of
I use Cygwin 32-bit all the time on Windows 10 x64.
--Sam
On Tue, Jun 12, 2018 at 7:31 PM Alejandro Benitez <
benitezalejandroe...@outlook.com> wrote:
> Hi,
>
> I have a 32 bit cygwin installation of 8 years of age in an amd64 PC with
> 2 GB of RAM with Windows 10. So far it's been so good. I
Greetings, Matt Nicholas!
> Hi Jon,
> Thanks for the additional comments.
> The two keyboard layouts that are installed are "ENG US" and "ENG INTL".
> (These are the two I see when I toggle through them using Key>+space.)
Why? Do you need the INTL one? If not, just remove it.
> I just
Greetings, Alejandro Benitez!
> I just don't know what I'll need to tweak /
> migrate so that the new Windows installation installed on top of the same
> drive that currently holds the 32 bit cygwin knows it's there. I'm betting
> some registry entries and environment variables. Does anyone know
Sven Eden writes:
> Doing a simple stat on / if (and only if) the UNC lookup
> fails, does not endanger anything. It wouldn't break
> anything or do any other damage. Besides from adding an
> additional <0.01s lag to any failed access that *really*
> meant a network share.
>
> So no. Adding this
On 2018-06-13 05:11, Christian Franke wrote:
Ivan Shynkarenka wrote:
I use x64 bit Cygwin and it failed in my home, work and Appveyor. I add
cygcheck.out with my environment.
I'm sorry about misspell prefix space in my prev example. Please try the
following one:
#include
#include
int
On 06/12/2018 08:14 AM, Sven Eden wrote:
Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr
Von: "Eric Blake"
Then fix your script to provide 3 slashes instead of 2. Only 2 slashes
has the magic UNC behavior.
It is not my script. *my* scripts are portable by all means.
Good to know!
That
On 6/12/18, Sven Eden wrote:
>> Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr Von: "Eric Blake"
>> Then fix your script to provide 3 slashes instead of 2. Only 2 slashes
>> has the magic UNC behavior.
>
> It is not my script. *my* scripts are portable by all means.
>
>> That is, if you have a
> Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr
> Von: "Eric Blake"
> Then fix your script to provide 3 slashes instead of 2. Only 2 slashes
> has the magic UNC behavior.
It is not my script. *my* scripts are portable by all means.
> That is, if you have a script that is concatenating:
>
>
Ivan Shynkarenka wrote:
I use x64 bit Cygwin and it failed in my home, work and Appveyor. I add
cygcheck.out with my environment.
I'm sorry about misspell prefix space in my prev example. Please try the
following one:
#include
#include
int main(int argc, char** argv)
{
std::string
On 2018-06-12 07:14, Sven Eden wrote:
>> Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr
>> Von: "Eric Blake"
>> Then fix your script to provide 3 slashes instead of 2. Only 2 slashes
>> has the magic UNC behavior.
> It is not my script. *my* scripts are portable by all means.
>> That is, if you
16 matches
Mail list logo
