THANK YOU!!!
~Ubuntu~
On Fri, May 3, 2024, 7:35 AM elextr ***@***.***> wrote:
> The issue you have is that the 4th quote (after the %f) is not an ASCII
> quote, but U+201C Left Double Quotation Mark. Just replace the command with:
>
> Wow eagle eyed!!
>
> —
> Reply to this email directly,
THANK YOU!!!
~Ubuntu~
On Fri, May 3, 2024, 7:33 AM Colomban Wendling ***@***.***>
wrote:
> gcc -Wall -o "%e" "%f“ `pkg-config --cflags gtk+-3.0`
> -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_0 `pkg-config --libs gtk+-3.0`
>
> The issue you have is that the 4th quote (after the %f) is not an ASCII
> The issue you have is that the 4th quote (after the %f) is not an ASCII
> quote, but U+201C Left Double Quotation Mark. Just replace the command with:
Wow eagle eyed!! :eyes:
--
Reply to this email directly or view it on GitHub:
> ```shell
> gcc -Wall -o "%e" "%f“ `pkg-config --cflags gtk+-3.0`
> -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_0 `pkg-config --libs gtk+-3.0`
> ```
The issue you have is that the 4th quote (after the `%f`) is not an ASCII
quote, but U+201C *Left Double Quotation Mark*. Just replace the command
I did enter a comment, don't know if that will re-open #3863.
First time using github except to download dban, knoppix std & chirp, never
to ask for help.
Thanks,
Bill
On Fri, May 3, 2024, 3:56 AM W. Sherman ***@***.***> wrote:
> I tried to edit 3863 and post last email and it's screenshot but
Using github is a hit-or-miss thing with me as I usually don't have internet
access. Only reason I do now is I'm in the hospital soon to be transferred back
to the Wound Care Center, that's why I've been using email not understanding
that would force a "Closed" status. Hopefully This will
I tried to edit 3863 and post last email and it's screenshot but it is
flagged as closed.
Can it be changed back to open or do I need to start a new issue
referencing 3863?
On Fri, May 3, 2024, 3:15 AM elextr ***@***.***> wrote:
> Your image did not come through.
>
> As I said above, you should
Your image did not come through.
As I said above, you should interact via the github website. Github is not a
mailing list, it is a website, and emails are largely intended for
notifications. Although you can post via email the variation in the behaviour
of mailing tools means many
I went back to the link you mentioned, Yes it does have the beginning and
ending stars I never placed them in the edit window. What I have in the
entry lines DO NOT. I've attached a screenshot of my
*Geany -> Set Build Commands*
window.
Thank you again.
On Fri, May 3, 2024 at 2:20 AM elextr
Please post the string from the build entry in github, not via email, the
string you have posted
[here](https://github.com/geany/geany/issues/3863#issuecomment-2091366390)
starts and ends with `*`.
--
Reply to this email directly or view it on GitHub:
Yes - one line.
I ran that line through a text editor & word processor I did not see a
single * in it.
The compile part works fine.
Just manually upgraded gcc (9.04 to 11, maybe something was outdated, no
luck). Wish I knew which file was the issue and where to look, only have
one "c" file I
Note that the problem is nothing to do with Geany (or codeblocks) its the
command you are entering. The best approach is to get commands to work in the
command line and then paste them into tools.
--
Reply to this email directly or view it on GitHub:
Closed #3863 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3863#event-12691206525
You are receiving this because you are subscribed to this thread.
Message ID:
Also I presume its all one line in the build command entry?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3863#issuecomment-2092040960
You are receiving this because you are subscribed to this thread.
Message ID:
Ok, your problem is that for some reason the website has a `*` at the start and
end of the command, those should not be there.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3863#issuecomment-2091968938
You are receiving this because you are
Using Synaptic I just re-installed all the files for gtk+ 3.0 wondering if
something got messed up from a long time ago. No improvement.
On Thu, May 2, 2024, 3:24 PM W. Sherman ***@***.***> wrote:
> Forgot - Error Message always:
>
> */bin/sh: -c: line 1: unexpected EOF while looking for
Forgot - Error Message always:
*/bin/sh: -c: line 1: unexpected EOF while looking for matching `"'*
On Thu, May 2, 2024 at 3:21 PM W. Sherman ***@***.***> wrote:
> I've went over that line character by character (added the space as you
> recommended), all backticks are matched (unless I'm
I've went over that line character by character (added the space as you
recommended), all backticks are matched (unless I'm missing something, new
to Linux programming never had this issue with windoze). The line cut &
pasted from the "Set Build Commands" is:
*gcc -Wall -o "%e" "%f“ `pkg-config
Well, the original error message indicates the backticks don't match, maybe
post the text from the build command entry (not from the website) on a line by
itself with a line of ``` before and another after it so its not recognised as
markdown. If we can't see exactly what you are inputting
No change. Still vigorously researching on my end.
Luckily I brought my laptop with me to the hospital so I've got plenty of
time (no improvement in 3 days).
Thanks again,
Bill
On Thu, May 2, 2024, 4:45 AM elextr ***@***.***> wrote:
> Try a space between the "%f" and the text you added.
>
> —
>
Try a space between the `"%f"` and the text you added.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3863#issuecomment-2089920282
You are receiving this because you are subscribed to this thread.
Message ID:
Did not mean any disrespect just thought it might have been quicker. I'll
learn - first post to github.
Actually he had the changes listed in his "Comments" section for cut/paste
where C commands first entry is named "Compile", and should contain the
following: *gcc -Wall -c "%f".*
Add the
> ALL settings are default with the exceptions mentioned in that youtube video.
You are asking for help, so requiring people to watch a video to be able to
help you means you have reduced the number who will bother, they simply don't
have time.
As I said, the default "Build" operation for C
ALL settings are default with the exceptions mentioned in that youtube
video. I'm having the same issue with Code::Blocks.
Ubuntu 20.04 LTS
Geany 2.0 Build date: 4-26-2024 from the repository.
Code::Blocks 20.03 also from repository.
Gtk+ 2.0 & 3.0 are installed and verified as well as being
The terminal setting has nothing to do with the Build command. The default
build command for C does not use "/bin/sh". What have you set the build command
to?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3863#issuecomment-2089335228
You are
25 matches
Mail list logo
