Git Product home page Git Product logo

Comments (7)

realh avatar realh commented on July 28, 2024

TBH I had noticed that before, but I didn't bother doing anything about it, my excuse being that gnome-terminal has the same issue. I'm glad you think having an "always show tab bar" option is a good solution, because it's probably easier than keeping track of whether a window has gone off screen and it solves another issue too.

Please could you check the latest svn, or would you rather wait for a new release?

Original comment by: realh

from roxterm.

realh avatar realh commented on July 28, 2024

Thanks for putting something together so quickly. I got the project from svn, but I wasn't able to compile it. I strongly suspect I'm doing something wrong - this is the first time I've ever worked with a project under automake. I write very simple programs that don't have to deal with multiple languages, character encodings, and flavors of Linux, so I've never ventured beyond simple makefiles. When you're ready to do another release, that will be soon enough.

Original comment by: tonynewman

from roxterm.

realh avatar realh commented on July 28, 2024

It would be good if you could test it before I make a release. To build it from svn you need automake, autoconf and libtool installed, and run 'apt-get build-dep roxterm' too to make sure you've got everything else needed. Then run bootstrap.sh before configure and make as usual.

Or do as above as far as the apt-get then build a debian package: checkout the debian bits too. While in the roxterm directory:

svn co https://roxterm.svn.sourceforge.net/svnroot/roxterm/trunk/debian

Then run bootstrap.sh then 'debuild -uc -us'. If all goes well you'll have a new .deb file in the parent directory.

Original comment by: realh

from roxterm.

realh avatar realh commented on July 28, 2024

Ok, progress... but not success.
I don't mean to make it your job to teach me how to build the project, but I could use a little more guideance.

After making sure automake, autoconf and libtool were installed, and then running 'apt-get build-dep roxterm' - all of which seemed to work fine, here are the last few lines displayed after running bootstrap.sh...

-=-=-=-=-=-=-=-=-=-=-=-=-=-
configure.ac:6: installing ./install-sh' configure.ac:6: installing ./missing'
src/Makefile.am: installing ./depcomp' Makefile.am: installing ./INSTALL'
Makefile.am: required file ./NEWS' not found Makefile.am: required file ./README' not found
Makefile.am: required file ./AUTHORS' not found Makefile.am: required file ./ChangeLog' not found
Makefile.am: installing `./COPYING' using GNU General Public License v3 file
Makefile.am: Consider adding the COPYING file to the version control system
Makefile.am: for your code, to avoid questions about which license your project uses.
autoreconf: automake failed with exit status: 1
tonyn@doozer:~/cproj/roxterm/trunk/roxterm$
-=-=-=-=-=-=-=-=-=-=-=-=-=-

If I then run 'debuild -uc -us' anyway, I get the following...

-=-=-=-=-=-=-=-=-=-=-=-=-=-
tonyn@doozer:~/cproj/roxterm/trunk/roxterm$ debuild -uc -us
debuild: found debian/changelog for package roxterm in the directory
/home/tonyn/cproj/roxterm/trunk
but this directory name does not match the package name according to the
regex PACKAGE(-.+)?.

To run debuild on this package, see the --check-dirname-level and
--check-dirname-regex options; run debuild --help for more info.
tonyn@doozer:~/cproj/roxterm/trunk/roxterm$
-=-=-=-=-=-=-=-=-=-=-=-=-=-

Am I starting things in the wrong directory?

Thanks for your patience...

Original comment by: tonynewman

from roxterm.

realh avatar realh commented on July 28, 2024

Hopefully the bootstrap errors don't matter, although it's probably necessary to create the ChangeLog:

svn log > Help/Changes
ln -s Help/Changes ChangeLog

Then it looks like you've got the debian directory in the wrong place. It needs to be inside the inner roxterm directory ie roxterm/trunk/roxterm/debian in your case, with the cwd set to roxterm/trunk/roxterm.

Original comment by: realh

from roxterm.

realh avatar realh commented on July 28, 2024

Success! (finally)

I now have three things:

  1. a working build environment for RoxTerm
  2. a working example of how to build a project for Debian
  3. a new version of RoxTerm where the "always show tab bar" feature works perfectly.

Of course, #3 is the one you are most interested in. I took your advice and built a Debian package using debuild, and it installed without problems. I found I had to create symlinks to AUTHORS,, NEWS, and README (in addition to the link for Changelog you mentioned ) before the bootstrap.sh script would complete successfully and create Makefile.am.

I use a light yellow for the background, so the white 'active' tab and the gray 'inactive' tabs are easy to see, despite there being no line or other separator between the tab bar and the text area. I'm not sure the extra pixels needed to separate them is worth it, at least for my color scheme. A white text area looks a little odd with only one tab, but with the tab area at the top or bottom of the window, the scroll bar helps define the text area as separate from the tab bar.

There's a little interaction between the tab bar placement choice and the always-show checkbox. If always-show is checked, it overrides the "hidden" selection of the placement choice, and makes the tab bar visible as if "Top" was selected. I expect if someone chooses that combination, then that's as good a way of dealing with it as any.

I mentioned earlier I'm using Xfce for my desktop, but I don't think I said what "flavor" of Debian I use - testing. (less likely to break things than unstable, and no jarring transition when stable changes to a new release).

Anyway, thanks for adding the feature, and guiding me in creating the package. If there is anything else you would like for me to try with RoxTerm, please let me know.

Original comment by: tonynewman

from roxterm.

realh avatar realh commented on July 28, 2024

I'm glad to hear it works, I've gone ahead and released it. It's s shame about the clash with the "hidden" pseudo-position. The current behaviour is accidental TBH, but I think I'll leave it that way rather than try to make them interact with each other, because it's easier all round.

Original comment by: realh

from roxterm.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.