xfce4-terminal is a gtk/vte based terminal like gnome-terminal, another option (among many).
--
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-osx/issues/3#issuecomment-251581989
That works but might be too minimal for me in that the text is very small and there's no way to change it.
Although, 20 lines might be optimistic for the script as inspection of my current wrapper code for Vte
(which just puts it in a scrolled window and gives cut/paste functionality) is about 60 lines.
--
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-osx/issues/3#issuecomment-251580115
> I also might write a 20 (or so, excluding the GPL copyright notice) Python/PyGObject script that would provide a program with the essential functionality of GNOME Terminal without all the frills.
Or just install xterm from the repo.
--
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-osx/issues/3#issuecomment-251577902
I thought about twiddling the environment inside my programs as you suggest but discounted it after I discovered that I got the same problem with geany's terminal if I launched geany directly from the command line inside the GNOME Terminal as this indicated that Python probably (if not definitely) wasn't implicated.
I'm going to avoid the problem by not using GNOME Terminal anymore. I mainly only use it when I'm testing my GUIs and need to be able to see any gumph that Gtk spits out to standard error or Python exceptions that I've failed to catch. Even though it might be wasteful of resources using geany for just its terminal I can use the terminal of a geany instance to achieve this end.
I also might write a 20 (or so, excluding the GPL copyright notice) Python/PyGObject script that would provide a program with the essential functionality of GNOME Terminal without all the frills.
--
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-osx/issues/3#issuecomment-251577687
@pwil3058 as a Python-specific workaround, you might do something like (untested):
```python
import os
env = dict(os.environ)
env["PS1"] = "\\w \\$"
# or something like:
# env["PS1"] = env.get("PS1", "\\w \\$")
subprocess.Popen(["geany", "-i"], env=env)
```
--
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-osx/issues/3#issuecomment-251569987
I spoke too soon. I'm still seeing this problem but only under very peculiar circumstances in that it only happens if I launch geany from a Python script using:
subprocess.Popen(["geany", "-i"])
(also without the "-i") but (and here's the weird part) only if the Python code is being executed from within a GNOME Terminal or from within a program that was started from inside a GNOME Terminal.
Just made another test and it also happens if I launch geany directly from the command line in a GNOME Terminal. (The version I have installed is GNOME TERMINAL 3.20.2 and it may not be the case for other versions.)
If I start geany from the menu or using Python inside a program launched from the menu (or from a program launched from geany's terminal) I don't see the problem.
So it seems that there's some sort of weird interaction between geany and GNOME Terminal but I'm not sure if it's worth pursuing this issue any further.
--
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-osx/issues/3#issuecomment-251567959
Please tell me ijf there is an easy way to go to a line at a specific column? I have read the help regarding ctrl-L but it does not mention such a useful possibility? Thanks!
--
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/1253
Adding the -l to inside .bash_profile works as expected. Also check that you have "bash -l" inside Editor->Preferences->Terminal->Shell seems to have fixed the problem. Thanks.
--
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-osx/issues/3#issuecomment-251548278
This is a backport of two commits from universal-ctags which have a great potential to introduce conflicts: most importantly the use of C99 bool, true, false, but also the removal of vStringTerminate() which is not needed. Better to merge sooner than later.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1251
-- Commit Summary --
* ctags: Use bool definitions from stdbool.h
* ctags: drop vStringTerminate()
-- File Changes --
M HACKING (1)
M ctags/main/args.c (12)
M ctags/main/args.h (4)
M ctags/main/entry.c (14)
M ctags/main/entry.h (10)
M ctags/main/general.h (12)
M ctags/main/keyword.c (8)
M ctags/main/kind.h (2)
M ctags/main/lcpp.c (147)
M ctags/main/lcpp.h (6)
M ctags/main/lregex.c (51)
M ctags/main/main.c (8)
M ctags/main/main.h (2)
M ctags/main/mio.c (44)
M ctags/main/mio.h (4)
M ctags/main/options.c (89)
M ctags/main/options.h (68)
M ctags/main/parse.c (93)
M ctags/main/parse.h (24)
M ctags/main/read.c (63)
M ctags/main/read.h (14)
M ctags/main/routines.c (69)
M ctags/main/routines.h (10)
M ctags/main/sort.c (6)
M ctags/main/sort.h (4)
M ctags/main/strlist.c (44)
M ctags/main/strlist.h (12)
M ctags/main/vstring.c (7)
M ctags/main/vstring.h (3)
M ctags/main/xtag.c (32)
M ctags/main/xtag.h (8)
M ctags/parsers/abaqus.c (11)
M ctags/parsers/abc.c (23)
M ctags/parsers/asciidoc.c (12)
M ctags/parsers/asm.c (56)
M ctags/parsers/basic.c (15)
M ctags/parsers/c.c (459)
M ctags/parsers/conf.c (17)
M ctags/parsers/css.c (18)
M ctags/parsers/diff.c (7)
M ctags/parsers/docbook.c (17)
M ctags/parsers/erlang.c (19)
M ctags/parsers/fortran.c (215)
M ctags/parsers/go.c (72)
M ctags/parsers/haskell.c (9)
M ctags/parsers/haxe.c (22)
M ctags/parsers/jscript.c (186)
M ctags/parsers/json.c (31)
M ctags/parsers/latex.c (21)
M ctags/parsers/lua.c (13)
M ctags/parsers/make.c (44)
M ctags/parsers/markdown.c (16)
M ctags/parsers/matlab.c (10)
M ctags/parsers/nsis.c (13)
M ctags/parsers/objc.c (82)
M ctags/parsers/pascal.c (72)
M ctags/parsers/perl.c (79)
M ctags/parsers/php.c (121)
M ctags/parsers/powershell.c (46)
M ctags/parsers/python.c (72)
M ctags/parsers/r.c (8)
M ctags/parsers/rest.c (15)
M ctags/parsers/ruby.c (68)
M ctags/parsers/rust.c (142)
M ctags/parsers/sh.c (13)
M ctags/parsers/sql.c (170)
M ctags/parsers/tcl.c (13)
M ctags/parsers/txt2tags.c (17)
M ctags/parsers/verilog.c (39)
M ctags/parsers/vhdl.c (45)
-- Patch Links --
https://github.com/geany/geany/pull/1251.patchhttps://github.com/geany/geany/pull/1251.diff
--
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/1251
Where do you set PS1? Normally Mac terminal runs bash as a login shell (which Geany does now too by defaulting to "bash -l" to grab the system settings of PS1) so you have to set PS1 inside .bash_profile (.bashrc won't be used). For me using
```
PS1="\w \$"
```
inside .bash_profile works as expected. Also check that you have "bash -l" inside Editor->Preferences->Terminal->Shell. If you have just "bash" there then bash isn't run as a login shell and you have to set PS1 inside .bashrc. What does "echo $PS1" say when you run it inside Geany's VTE? I guess it's something different than "\w \$".
--
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-osx/issues/3#issuecomment-251433229