Happy to open another issue so as to not hijack this one, but I would also
personally settle for defaulting to the Desktop directory (or, if not truly
defaulting, then allowing the addition of a config option to specify a default
directory).
The way Geany works right now (having checked on
Actually I suspect that set of rules is from the SVN days where "commit" refers
to what is called "merge" now in the Github days. Maybe the title should
change and then the rules all re-examined?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
This is suggested due to a conversation in IRC with @elextr @codebrainz.
The squashing if done, should be done by the person merging, otherwise
the submitter has to rebase or force-push...
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2059
closes #2054
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2058
-- Commit Summary --
* geany-status.m4:replace hyphens with text
-- File Changes --
M m4/geany-status.m4 (3)
-- Patch Links --
Yeah, since its just prettifying text its fine to remove.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2054#issuecomment-455401169
I'm indifferent, any of the above is fine by me.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2054#issuecomment-455400757
That would work, but imo adding a condition (and extra code) for this case may
be too clunky.
Another option would be to remove the repeating hyphens as a separator (and
therefore the use of `seq` and replace it with a line break and some text. Ex:
```
config.status: executing libtool
> This issue is very trivial and only appearance-related.
Agree. Would it be enough to simply pipe stderr to `/dev/null` to hide the
error on other systems?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Yeah, gseq, which is apparently in the coreutils package.
> As I said, geany is in openbsd ports, so it builds there, so either seq is
> available or configure is being modified by the ports build?
I don't see it's being modified. The maintainer's probably ignoring the output.
All seq is used
Yup, "All the binaries are prefixed by the letter g to differentiate them with
the standard applications with the same name."
[from](http://ports.su/sysutils/coreutils)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> I installed the coreutils package, but seq still isn't available.
Do they call it `gseq` or something?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2054#issuecomment-455394772
As I said, geany is in openbsd ports, so it builds there, so either seq is
available or configure is being modified by the ports build? I guess this is
your chance to expand your BSD knowledge and learn how ports are built :grin:
Disclaimer: I am not a BSDist
--
You are receiving this
Thanks for explaining.
> Did you try installing [the `seq`
> utility](https://en.wikipedia.org/wiki/Seq_(Unix))? It's part of GNU
> Coreutils, and seems to also [be available on
> BSDs](https://man.openbsd.org/FreeBSD-11.1/seq.1).
Hmm.. that seems to be showing results for FreeBSD man pages
Closed #2055.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2055#event-2081695165
You should only use
[POSIX}(http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html)
shell commands. See comments on #2054
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> may be a a good solution, if that's shell-portable.
sadly not
As @codebrainz said, its running the `seq` program, so its not shell related.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Did you try installing [the `seq`
utility](https://en.wikipedia.org/wiki/Seq_(Unix))? It's part of GNU Coreutils,
and seems to also [be available on
BSDs](https://man.openbsd.org/FreeBSD-11.1/seq.1). The problem with using
special shell-builtins/syntax is that it may not be compatible with
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2057
-- Commit Summary --
* configure.ac:expand comment for AC_USE_SYSTEM_EXTENSIONS
-- File Changes --
M configure.ac (6)
-- Patch Links --
Thanks @eht16 , that was enough of a hint. The new page is now linked on the
front "HowTo" page.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2053#issuecomment-455337211
What do you want to achieve after all?
Geany packages exist already in Ubuntu.
And if you still want to compile yourself, `apt-get build-dep geany` will
install anything for you which is necessary to build Geany yourself.
--
You are receiving this because you are subscribed to this thread.
Closed #2053.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2053#event-2081267788
@masatake We remap ctags kind letters using the tables here:
https://github.com/geany/geany/blob/master/src/tagmanager/tm_parser.c
into TMTagType
https://github.com/geany/geany/blob/master/src/tagmanager/tm_parser.h
which we use internally in Geany code. In the past we didn't have these
@andy5995 pushed 1 commit.
854c98441e649543765b234b73fb13b7971757eb remove unnecessary macro
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
This is related to #2053
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2056
-- Commit Summary --
* autogen.sh:don't instruct user to run "make" unconditionally
-- File Changes --
M autogen.sh (2)
M configure.ac (15)
-- Patch
fixes #2054
I don't know enough about shells to know how portable this patch is. All
I can say for sure is that it works with ksh and bash.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2055
-- Commit Summary --
* geany-status.m4:don't
https://github.com/geany/geany/blob/c825b581bfabf6912eeb737a4af607e70c6c07a9/m4/geany-status.m4#L30
Due to `ksh` being the default shell on OpenBSD. But changing that line to
something like
for i in {1..$total};
may be a a good solution, if that's shell-portable.
```
config.status:
I started a page at https://wiki.geany.org/howtos/bsd/compiling
There's not much to it, as when I compiled geany on my BSD system there was
nothing much I needed to do different from when I compile it on Linux.
I created it as a separate page under bsd/ as I figured that would allow for
Closed #2049.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2049#event-2080300774
> > About howtos, it's probably mostly because nobody wrote one, which you
> > could do if you felt like it as it's a wiki ;)
>
> Yeah, I kinda do feel like it :)
I created https://github.com/geany/geany/issues/2053 for that.
--
You are receiving this because you are subscribed to this
I'm going to start a section on the wiki for building Geany on BSD (follow-up
to https://github.com/geany/geany/issues/2049).
At https://wiki.geany.org/howtos/start when I click to edit the page, hardly
any of the existing data shows up (see screenshot). Is this a permissions issue?
@b4n, I don't understand well "internally" means.
I guess Geany uses kind names only after getting tags information from ctags.
ctags may return 'p' or 'f' kind tags. Both are unified to "function" by
calling
ctagsGetKindName.
Am I correct?
--
You are receiving this because you are
As I'm pretty new to BSD, my goal was just a little testing, to see if I could
build geany ok and to see if any docs about it needed updating.
>About howtos, it's probably mostly because nobody wrote one, which you could
>do if you felt like it as it's a wiki ;)
Yeah, I kinda do feel like it
Normally it doesn't change anything, at least not anymore, we should only be
using the kind letter internally.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Again, I suggest using git-subtree to import u-ctags, then make our changes on
top (build system, remove/swap parsers, geany-specific changes). Following
that, we can import new versions with a single "git subtree pull" command while
maintaining our changes.
--
You are receiving this because
The basic PR that re-organised things to allow that (#1263) was only committed
late last year but it was then several years old and #2018 just brings it more
up to date, so we don't actually have a defined workflow yet.
I was thinking something similar to the way we manage Scintilla and its
@masatake Geany is slowly moving towards being able to use as much upstream
ctags unchanged as possible, see #1263 (merged) and #2018.
But nobody has dared to look at Geany's c.c yet :)
It has a lot of history as it was changed significantly independently during
the period that ctags was
36 matches
Mail list logo
