Hello,
do I need to add something for the patch to be included in the geany repository?
I've seen you talked about some "filedefs/filetypes.*" configuration, does it mean it would replace such definitions in the future?
Just a normal build: but a strange configure error did occur.
$$$
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
configure: error: No C++ compiler not found. Please install a C++ compiler.
$$$
I found it's just a ``which`` in configure.in.
QQQ
# check for C++ compiler explicitly and fail if none is found, do this check
# after AC_PROG_CXX has set the CXX environment variable
which $CXX >/dev/null 2>&1
if test "x$?" != "x0"; then
AC_MSG_ERROR([No C++ compiler not found. Please install a C++
compiler.])
fi
QQQ
I didn't know that the ``which`` utility was considered a compiler. :p
How about just using a shell builtin, ``hash``, ``type -P`` or just ``eval
$CXX --version`` as a test instead?
------------------------------------------------------------------
configure.in:18 : which $CXX >/dev/null 2>&1
configure.in:51 : GIT=`which git 2>/dev/null`
configure.in:60 : SVN=`which svn 2>/dev/null`
Found 3 matches for "which".
--
-Erik S
[CCing geany devel list, using the address I'm subscribed with to avoid
moderation]
On Tue, Dec 15, 2009 at 10:45:25PM +0000, Ximin Luo wrote:
> Damián Viano wrote:
> > I used a text file with (created with echo 'try to replace me \t' >test_file):
> >
> > try to replace me \t
> >
> > [snip: me seeing only the third case stated here]
>
> My mistake; "Use regular expressions" needs to be on.
I see, I can reproduce it now. But there's more to it,
> In "try to replace me with \t", with Find = "me":
This is the result with:
"Use regular expressions" ON
"Use escape sequences" OFF
> Replace = "\t" replaces "me" with a tab
> Replace = "\\t" replaces "me" with a backslash followed by a tab
> Replace = "\\\t" replaces "me" with two backslashes followed by a tab
"Use regular expressions" ON
"Use escape sequences" ON
Replace = "\t" replaces "me" with a tab
Replace = "\t" replaces "me" with a tab
Replace = "\\t" replaces "me" with a backslash followed by a tab
> The correct behaviour (iirc) is to escape "\\" into "\"; so that:
"Use regular expressions" OFF
"Use escape sequences" ON
> Replace = "\t" replaces "me" with a tab
> Replace = "\\t" replaces "me" with the literal string "\t"
> Replace = "\\\t" replaces "me" with a backslash followed by a tab
Let's hear Enrico's , Frank's and/or Nick's (upstream authors) on this.
Thanks for your report and follow-up Ximin.
Damián.
In last 3 weeks i've in development of new plugin-wrapper of geany
plugin-api for python. Main idea - ability to write plugins in python with
pygtk and mini-abstract level for geany structures.
I've encountered with problem. I need to build bridge and for scintilla, but
python have only 3 wrappers: pyscintilla(rip in <2004), pygtkscintilla(rip
in 2004), pyqscintilla(rip with pyqt, because pyside don't have wrapper).
Best way - pyqscintilla. But i want to write good and usefull mini-engine.
And i trying to google information about this question. I found many mails
in lists, where talking about scintilla and gtksource view. Main thing -
scintilla is going to be RIP'd, cuz development rate too small and
community, who interests in this library, very small. Best way - use
gtksourceview, becouse it now(in 2.9) have got all necessary functionality
and going to be best widget for source editor.
As i think, now need to start moving onto gtksourceview as parallel work
with 0.19. And at 0.20 fully go to gtksourceview.
At the end, gtksourceview is "native" to gtk+, unlike to scintilla. And, of
cause, pygksourceview have very good wrapper to python.
What are you think?
Some links:
1) Old features list - http://projects.gnome.org/gtksourceview/features.html
2) Current changes and goals and information -
http://live.gnome.org/GtkSourceView
3) References for latest version -
http://library.gnome.org/devel/gtksourceview/unstable/
Thanks for your answers.
I totally agree that a popup dialog for that would be ugly and annoying.
However, I think that this issue is quite important, since enabling that
feature by default can be strongly distrurbing for PHP development.
After some thinking, I would suggest that :
- the feature "*new line at end of file*" would be a drop-down list
instead of a checkbox, with options "*according to file type*"
(default), "*always*", "*never*"
- when option "*according to file type*" is selected :
- when (for example) a C/C++ file is saved, a new empty line is
automatically added if necessary
- when a PHP (or Javascript, CSS, HTML, SQL, XML, YML...) file is
saved, no new empty line is added
- details about file types requiring a "final empty line" or not,
would be available in the manual.
This way, Geany's default behavior would be convenient for all
programming languages (but user can "force" the behavior to whatever he
prefers), and the user wouldn't be annoyed by any warning message.
Maxime
Enrico Tröger a écrit :
> On Sat, 28 Nov 2009 11:01:52 +0100, Frank wrote:
>
>
>> On Thu, 26 Nov 2009 19:02:10 +0100
>> Maxime Pacary <mpacary(a)winsoft.fr> wrote:
>>
>>
>>> A nice colleague knowing better Geany told me that this could simply
>>> be disabled in preferences > files ; so please ignore that bug
>>> report, sorry. However, it could be nice to warn the user if he works
>>> on PHP files while having the feature "new line at end of file"
>>> enabled.
>>>
>> I don't see any big reason for adding a warning, maybe a pop-up or
>> something like that. In time this will be more annoying as helpful from
>> my point of view. I recommend just deactivate the feature and ensure to
>> insert empty line manual in case its needed.
>>
>
> Exactly.
> If you don't want Geany to insert new blank lines at the end of files,
> deactivate this feature. Adding a warning in whatever way, is just more
> annoying than helpful.
>
>
> And to be able to receive further answers and be able to send messages,
> you first need to subscribe to this mailing list. Thanks.
>
> http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
>
>
> Regards,
> Enrico
>
>
Dominic >> I like the website :) I have just one remark for the CodeNav
plugin' "about" section : " Actually, it will make it possible to : - switch
between header and implementation - go to a file by typing its name" -> you
should add line breaks before the "-".
And I definitely should implement this second part :p
Lionel.
Dear Geany devs,
It would be nice if the 'find in files' dialog would remember the last
searched path. Ideally there would be a button that sets the path to
that of the active document. (lik the file browser sidepane has)
I often search from my project's base dir so every time I open tht
'FiF' dialog I have to reset the path...
-tnx!-
Harold
As i say in first message, all ok. Now folding and highlight engine can
replace scintillas functionality. But only in last(2.9) version, which now
marked "unstable". It might be good time to start changing, because when 2.9
will be "stable", geany might be already with gtksourceview and all features
what it provides.
Hi guys, it's me again.
First, I'd like to say sorry about tons of emails I sent last time by
accident. Actually I did not notice that until I took a look at
geany-devel archives tomorrow. Definitely, the experiment with `git
format-patch' was unsuccessful...
Second, there was a little question in my previous mail. As I did not
receive any answer, I decided to make code changes as little as
possible. Maybe I should have done so immediately, without asking that
question... Anyway, the result is the last (#8) patch for sm branch.
Now I consider XSMP support complete, some testing is required.
Below are patches for sm branch that have not been applied yet. I sent 7
of those within the tons of emails I mentioned earlier. It is easier to
access them in a single email, so I attach them here. The text below
the filename of a particular patch is the proposed commit message for
the patch.
Feel free to ask questions about these patches and to point
to mistakes which I possibly made there.
-------------------- 8< --------------------
[1.files.patch]
Extract SM-related code into separate sm.{c,h} files, make some
refactoring, and write code comments for Doxygen.
[2.sm_finalize.patch]
Add sm_finalize().
[3.fix-restart-command.patch]
Fix restart command.
[4.fix-interaction.patch]
Handle "Interact" message properly.
[5.noinstance-behaviour.patch]
Make --new-instance imply --no-session.
[6.nosession.patch]
Handle --no-session properly.
The previous commit allows us to change --no-session command line option
handling back to normal. The issue was described in a FIXME section
inside src/sm.c, the section is now deleted.
[7.fix-filenames.patch]
Use `GeanyDocument.file_name's instead of `GeanyDocument.real_path's in
restart command like Geany session management facilities do.
[8.optentries.patch]
Add "reverse parser" for GOptionEntry. Handle all command-line options.
-------------------- 8< --------------------
Best regards,
Eugene.
Hi guys,
as promised in a mail few weeks ago I'm working on a new website for
plugins.geany.org. A first impression is already available at [1].
Any feedback is appreciated.
Note that there is still content missing about some plugins since I
didn't found time yet to work on every plugin page.
Just for your information, since I will maintain the site in future: I
developed a small process (mainly for me myself) to make sure the
maintenance of the site will stay as easy as it is at the present. There
are some configuration files available for rst2html and HTML Tidy at
[2], [3] and [4]. A small description of the idea behind these files is
available at [5].
This process implicates, that any information provided on [1] will be in
sync with your README files. I would just add navigation features and
such things to make it easy for a visitor to navigate through the site
and maybe also fix some typos and other syntax concerned issues but not
change any content related to your plugins. Actually, this already
happened for some plugins as you can see at [1]. In cases I am doing
changes (like fixing typos) to README files, I'll write a mail including
a patch to the affected plugin developer.
Generating the content for the website from every README file means
also, if your README files are not up to date, the website also isn't.
For this reason I'd like to remember you to check your README files time
after time and see if any changes are necessary.
Please let me know what you're thinking of this prove of concept
(generating content from your README files) and maybe if you think there
are better ways to implement the site, I'd be happy about any
feedback. :)
I'm going for winter vacancies tomorrow and will be back in the
beginning of January, so most likely the site won't go live anymore this
year.
Wish you all a merry x-mas and a happy new year!
Best Regards,
Dominic
[1] http://plugins2.geany.org/index.php
[2] http://plugins2.geany.org/content/rst2html_config.conf
[3] http://plugins2.geany.org/content/rst2html_template.txt
[4] http://plugins2.geany.org/content/tidy.conf
[5] http://plugins2.geany.org/index.php?site=README
--
Dominic Hopf <dmaphy(a)gmail.com>
http://dominichopf.de/
Key Fingerprint:
A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D