<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Out of curiosity, what is the native language of many of the people
on this list?<br>
Quero saber, o que seja a língua principál das pessoas nesta lista
de e-mail?<br>
Sprechen Sie Deutsch?<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<span style="color: rgb(34, 34, 34); font-family: arial, sans-serif;
font-size: small; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: 16px;
orphans: 2; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); display: inline !important;
float: none; ">¿</span>Hablan Español?<br>
<br>
Ni Hau :-)<br>
<br>
Steve<br>
<br>
<div class="moz-cite-prefix">On 11/28/2012 05:08 PM, Lex Trotman
wrote:<br>
</div>
<blockquote
cite="mid:CAKhWKDMRnj1hQhjmh9XjJppHJZftRG=NBtF22_rKyDpS3+ePkg@mail.gmail.com"
type="cite">
<pre wrap="">On 29 November 2012 05:25, Steven Blatnick <a class="moz-txt-link-rfc2396E" href="mailto:steve8track@yahoo.com"><steve8track@yahoo.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Replies below. I hope nobody is annoyed that the new guy is emailing so
much :-)
</pre>
</blockquote>
<pre wrap="">
Of course not, but be aware that many Geany devs do not have English
as their first language so the bigger the email the fewer read it
tl;dr :)
(Not that I'm innocent of verbosity of course :)
Also please keep your emails to text only. Mailers don't agree well
on how HTML should render and > quotes don't work right.
[...]
</pre>
<blockquote type="cite">
<pre wrap="">Maybe if it's just a flag it could be dependent on what it's building
against? Though I hate to support different features for different
dependencies... If they end up keeping that feature, I hope we could use it.
</pre>
</blockquote>
<pre wrap="">
We try to avoid #ifdefs everywhere.
[...]
</pre>
<blockquote type="cite">
<pre wrap="">Instead, I think it would be more intuitive to put them all together like
GEdit's External Tools. It's simpler and more powerful I think. (Don't get
me wrong, I wouldn't be trying geany out if I thought gedit were better in
every way. Geany has a lot of customization GEdit lacked.) For those who
haven't used GEdit much, let me point out some of the features, as well as
ideas for improvement:
</pre>
</blockquote>
<pre wrap="">
The whole suggestion was tl;dr but let me point out that each of these
ways of running commands is different, for example compile commands
have their output scanned for error messages to show in the compiler
tab, execute commands do not have this, custom commands paste their
results in the buffer, etc. As I remember gedit didn't have these
things. So whilst combining them might in some ways be nice, I think
it is likely to confuse users who try to configure the wrong sort of
command in the wrong place.
[...]
</pre>
<blockquote type="cite">
<pre wrap="">I meant that we should add those features to the current file browser
plugin. I wasn't able to see those features in the context menu.
</pre>
</blockquote>
<pre wrap="">
Use the treebrowser plugin instead, add to that if you need to, keep
the filebrowser simple for Luddites like me :)
[...]
Cheers
Lex
_______________________________________________
Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Devel@lists.geany.org">Devel@lists.geany.org</a>
<a class="moz-txt-link-freetext" href="https://lists.geany.org/cgi-bin/mailman/listinfo/devel">https://lists.geany.org/cgi-bin/mailman/listinfo/devel</a>
</pre>
</blockquote>
<br>
</body>
</html>