From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id x0DIiJIL025236 for ; Sun, 13 Jan 2019 13:44:19 -0500 Received: by smtp.corp.redhat.com (Postfix) id 878D0103BAB2; Sun, 13 Jan 2019 18:44:19 +0000 (UTC) Received: from mx1.redhat.com (ext-mx08.extmail.prod.ext.phx2.redhat.com [10.5.110.32]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 80537101E5A5 for ; Sun, 13 Jan 2019 18:44:17 +0000 (UTC) Received: from mail-ot1-f50.google.com (mail-ot1-f50.google.com [209.85.210.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1770BC057F3B for ; Sun, 13 Jan 2019 18:44:16 +0000 (UTC) Received: by mail-ot1-f50.google.com with SMTP id a11so17490661otr.10 for ; Sun, 13 Jan 2019 10:44:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=eYKe1iQ3Up+J4/6mhEfeJpB6GXjL8QN38Po91mwx068=; b=FHlpbNIeYS5D3TiEldS8vzsgyl9HaBahk68vdmZvMNZEycI+e6v+N1ZRizE/DSen10 hJZBQb7kw3mFwpadd+lSxEcqcr9O2OtEjbGWtTAS+Dq+1796GKcPfkE8oMFfnYro4+K1 CA0QI5OBQwhMFmM2XgNdWdLH/TXLMUu7aTg8UKjWbiWo8rJR+iANbAE1/nxf0Rr2LLSL 4x0I7RNDXhwyktKQx4No7RYIbpKHDTXwhMAJh9qXHXwHyzAGtWR9KSplt09y9PQloxcI K/5QlNGN300AaqjyuN13fk4dobfp4u9fFZSWuxlzCm4ts6fk94yYJuERDqaVagzyWIct kmSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=eYKe1iQ3Up+J4/6mhEfeJpB6GXjL8QN38Po91mwx068=; b=r6GCqGpupjYwUWH2XmF5hg0/2mNX+IYfSS2FbVb2moYA5BvRGY7FUwMbKksZEFx0h3 KC67sE5gaKJZlDEfDLZCR0hx1q29TgbuUc3Bhd/Jg8O1nkBV5sIWFZkrNa+a1nbKct4g 3yHOIVxadWqp4Lz85TvtbBp0/lozQvsSlh5nMjVewexaSaGQuDMOcuxt6JN588W/QACw SzwaqOlDf5EHrbjEDQPa2LX5uWqXNpC/FMa5oAf4+yyliVcwk8n740dIi0FbA3HhlDge 4KfFv1IQaIfFOtZ/QC/mYXhbHvNtTMQ8q+6OXj8S0frlFdfT77tTIG6hLa+jpDAsVr/4 lTHg== X-Gm-Message-State: AJcUukd5STu5U0qtnLMpE0i+Z5E3wo1DFfjOUsJe9KUVBU8ztOrnmZTh KQZ4CeECzHBEMoA7L+FE4R9DUpOShE0LZIQPxV0akp5M X-Google-Smtp-Source: ALg8bN6BL7n13r7gxhswPGlCDHveGMPvv8VuAcG385sB0on+xFhyl9dOhIEG6V/697/crdijozjbLaVLTBbz0S/4Myg= X-Received: by 2002:a05:6830:120c:: with SMTP id r12mr15966321otp.252.1547405055040; Sun, 13 Jan 2019 10:44:15 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6830:2158:0:0:0:0 with HTTP; Sun, 13 Jan 2019 10:44:14 -0800 (PST) In-Reply-To: References: Date: Sun, 13 Jan 2019 18:44:14 +0000 Message-ID: Subject: Re: bash undocumented syntax error To: blinux-list@redhat.com Content-Type: text/plain; charset="UTF-8" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Sun, 13 Jan 2019 18:44:16 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Sun, 13 Jan 2019 18:44:16 +0000 (UTC) for IP:'209.85.210.50' DOMAIN:'mail-ot1-f50.google.com' HELO:'mail-ot1-f50.google.com' FROM:'mewtamer@gmail.com' RCPT:'' X-RedHat-Spam-Score: -0.11 (DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_PASS) 209.85.210.50 mail-ot1-f50.google.com 209.85.210.50 mail-ot1-f50.google.com X-Scanned-By: MIMEDefang 2.78 on 10.5.110.32 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-loop: blinux-list@redhat.com From: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: blinux-list@redhat.com List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2019 18:44:19 -0000 Yeah, an error of this type is hard enough to debug when you have access to the buggy code. Debugging from the error message alone is nearly impossible in cases like this. I will mention, however, that bash, and many other shells/scripting languages, aren't picky about single quotes versus double quotes in general, but can be quite picky that they're used consistently. E.g. if you start a string literal with single quotes, you'd better end it with single quotes, and if you start it with double quotes, you'd better end it with double quotes, but bash probably doesn't care which you use as long as the beginning and ending delimiters are the same. Probably about the best advice I can give without examining the code directly. -Jeff On 1/13/19, Linux for blind general discussion wrote: > On Sun, 13 Jan 2019, Linux for blind general discussion wrote: > >> The man page has nothing on unexpected end of file in it; searching for >> unexpected in that man page provides no mention of unexpected. > > Possibly I've missed the context for this if it's a new thread resulting > from a previous one (I am not up-to-date on this list). > > The error seems pretty self-explanatory. Bash expected more input when it > reached the end. > > I would expect that it was either looking for a closing quote (single or > double) or a closing bracket of some sort. > > what are you trying to do? > > Cheers, > Geoff. > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list >